-
Notifications
You must be signed in to change notification settings - Fork 199
add additional exports to public API #2910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
rchl
wants to merge
11
commits into
main
Choose a base branch
from
feat/public-api
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+52
−34
Open
Changes from 9 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
65b3237
add additional exports to public API
rchl 95db343
Point
rchl 9dbbbc7
Merge remote-tracking branch 'origin/main' into feat/public-api
rchl 75a19ae
more exports
rchl a97d5c8
add offset_to_text_position
rchl 72bf5b4
Point -> TextPosition
rchl 9db873f
convert to dataclass
rchl 2aecaef
Merge branch 'main' into feat/public-api
rchl 517f5fc
Merge branch 'main' into feat/public-api
rchl 12fc1ea
Merge branch 'main' into feat/public-api
rchl ff93322
offset_to_text_position -> offset_to_position
rchl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before we export these in the public API, could we also make the argument order consistent?
The exported
offset_to_point,offset_to_position,region_to_rangeandtext_document_position_paramstake the View as the first argument, whilepoint_to_offsetandposition_to_offsethave that as the second argument. I think it would be nice if all utility functions which take a View have it as the first argument.Changing the argument order in
point_to_offsetwould affectAnd in
position_to_offsetwould affectUh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we want to maintain backwards compatibility for those helper packages for now, we could leave these two functions witch current argument order in
views.pyand mark them as deprecated, but also copy them with the updated argument order into another file. And then just import the updated functions from the new locations for the public API (in__init__.py). Later when all helper packages are updated to the new argument order, we could remove the deprecated functions and just move the updated ones back intoviews.py.