MID-10415 Fix mapping property autocomplete matching#668
Open
kay1313 wants to merge 1 commit into
Open
Conversation
Resource wizard mapping property autocomplete used prefix-only and case-sensitive filtering. This meant that typing "name" found only "name", not "familyName" or "givenName", and typing "Name" found no matches.
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.
Summary
Fixed autocomplete filtering for focus object item paths used in mapping-related GUI fields.
Previously, the provider used prefix-only matching. Because of that, typing
namein the resource wizard inbound mapping MidPoint property field proposed onlyname, but did not propose other valid properties that contain the same text, such asfamilyNameorgivenName.The filtering now uses partial matching, so matching properties are suggested even when the typed text appears later in the property name. Matching is also case-insensitive.
Affected areas
The changed provider is
FocusDefinitionsMappingProvider. It is used by focus object property/item-path autocomplete fields in mapping and correlation screens.This affects suggestion filtering in places such as:
The change only affects autocomplete suggestions for focus object properties/item paths. It does not change mapping evaluation, resource schema handling, repository queries, or resource attribute autocomplete. The resource attribute selector already used partial case-insensitive filtering through a different provider.