refactor(web): split tokenization realignment from evaluateTransition 🚂#15191
Draft
jahorton wants to merge 2 commits intofeat/web/search-space-node-propagationfrom
Draft
refactor(web): split tokenization realignment from evaluateTransition 🚂#15191jahorton wants to merge 2 commits intofeat/web/search-space-node-propagationfrom
jahorton wants to merge 2 commits intofeat/web/search-space-node-propagationfrom
Conversation
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
keymanapp-test-bot
bot
changed the title
jahorton
force-pushed
the
feat/web/search-space-node-propagation
branch
from
b31bcad to
c303355
Compare
jahorton
force-pushed
the
feat/web/search-space-node-propagation
branch
3 times, most recently
from
beafeb6 to
36df714
Compare
jahorton
force-pushed
the
refactor/web/realign-tokenization
branch
from
49391d5 to
3473c6f
Compare
With the various ways that tokenizations can transition depending upon which potential inputs are applied, it's possible for multiple different tokenizations to transition into the same one. As such, there will no longer be "just one" way that a tokenization is reached. Accordingly, it's best to perform word-boundary realignment operations (splits, merges) separately from text-editing operations (inserts, deletes). Build-bot: skip build:web Test-bot: skip
…nization unit tests
jahorton
force-pushed
the
feat/web/search-space-node-propagation
branch
from
36df714 to
c2e0427
Compare
jahorton
force-pushed
the
refactor/web/realign-tokenization
branch
from
3473c6f to
4f257f5
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
With the various ways that tokenizations can transition depending upon which potential inputs are applied, it's possible for multiple different tokenizations to transition into the same one. As such, there will no longer be "just one" way that a tokenization is reached.
Accordingly, it's best to perform word-boundary realignment operations (splits, merges) separately from text-editing operations (inserts, deletes).
Build-bot: skip build:web
Test-bot: skip