fix(designer): Ensure OpenAPI token keys are normalized #5023
Conversation
This file contains 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.
Please check if the PR fulfills these requirements**
What kind of change does this PR introduce?
Bugfix (PAuto)
What is the current behavior?
Token title update compares normalized keys to non-normalized keys. This is fine for non-OpenAPI scenarios, but for OpenAPI tokens, normalized and non-normalized keys are necessarily unequal, and thus the comparison fails.
What is the new behavior
Tokens are normalized on both halves of the comparison, so the comparison succeeds.
Does this PR introduce a breaking change?
No
Screenshots or Videos of the intended change
LA
PA