change(web): remove unused transition-edit field 🔪#16071
Open
jahorton wants to merge 1 commit into
Open
Conversation
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
5631d8f to
702efa3
Compare
3948c1d to
82b9f18
Compare
702efa3 to
bc32ac3
Compare
82b9f18 to
0b97139
Compare
Build-bot: skip build:web Test-bot: skip
0b97139 to
c2816da
Compare
ermshiperete
approved these changes
Jun 17, 2026
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
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.
The
transitionEditfield ofContextTokenizationexisted to indicate how it was reached via transition - back when there was only one transition path under consideration. It was not actually utilized in any form from this location.Additionally, with epic/boundary-correction, each
ContextTokenizationinstance may be reached by multiple different paths and may even "cluster" these paths. There won't be a "single" path, so the field makes even less sense to maintain now than it did before. It's time to axe it.Build-bot: skip build:web
Test-bot: skip