-
-
Notifications
You must be signed in to change notification settings - Fork 130
refactor(web): implement token splitting on SearchPath / SearchSpace 🚂 #15023
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
Draft
jahorton
wants to merge
11
commits into
refactor/web/rename-and-doc-pending-tokenization
Choose a base branch
from
refactor/web/search-path-splitting
base: refactor/web/rename-and-doc-pending-tokenization
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.
Draft
refactor(web): implement token splitting on SearchPath / SearchSpace 🚂 #15023
jahorton
wants to merge
11
commits into
refactor/web/rename-and-doc-pending-tokenization
from
refactor/web/search-path-splitting
Conversation
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
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
f77c477 to
5dd11d5
Compare
b741e1d to
a6ccfd0
Compare
564acba to
3ab72c7
Compare
347f7ed to
fc97837
Compare
fc97837 to
2fc98eb
Compare
461fa4d to
449ebec
Compare
Once we support modeling of multiple paths to construct individual context tokens, it's notably less straightforward to split or merge the correction-search paths on the token level. It's instead wisest to implement this via the SearchSpace interface and its implementing types, which are designed to recursively model all relevant paths and thus can facilitate these operations more directly. Build-bot: skip build:web Test-bot: skip
2fc98eb to
e6cbc29
Compare
…refactor/web/search-path-splitting
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While token-splitting is currently implemented on
ContextToken, supporting splits (and merges) for a graph of SearchSpaces that converge and diverge as new keystrokes are added gets really tricky if kept in place. A cleaner way forward is to support.split()(and next, also.merge()) on theSearchSpacetype itself.To facilitate this, a few new additional properties are added to the
SearchSpaceinterface; these exist to exchange information with otherSearchSpaces andSearchSpacetypes as necessary to fully implement.split().Build-bot: skip build:web
Test-bot: skip