Priority of REST Client Config changed to Quarkus FQN, config key, simple name #45044
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.
This fixes a couple of problems:
The priority checks for properties were FQN, SimpleName, and config key. In cases where the Simple Name is the same (but the classes are in different packages), it would mess up the configuration. We should consider removing Simple Name as a possible combination. Here is also a related discussion: #44067 (comment)
Relocates for shared config keys used a single
Map
which override the relocate name when the config key is shared. It now uses aMap
with aList
to keep track of all possible relocations.