This repository was archived by the owner on May 21, 2025. It is now read-only.
Preventing override on blur after auto-match#476
Open
sangaman wants to merge 2 commits into
Open
Conversation
When override-suggestions and auto-match are both true, a match on originalObject occurs but is then overridden with a custom object on blur. This change sets a flag when an exact match is found that prevents override until the input text changes. Includes a test case that fails with old code but passes with these changes.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
When override-suggestions and auto-match are both true, a match on
originalObject occurs but is then overridden with a custom object on
blur. This change sets a flag when an exact match is found that prevents
override until the input text changes. Includes a test case that fails
with old code but passes with these changes.
This fix addresses issue #387 .