Repository navigation
Fix synthetic bean priority collisions - #3540
Merged
Merged
Conversation
manovotn
force-pushed
the
fix-synthetic-bean-priorities
branch
from
September 30, 2026 06:43
d1526ca to
b6a0581
Compare
manovotn
marked this pull request as ready for review
September 30, 2026 06:56
manovotn
force-pushed
the
fix-synthetic-bean-priorities
branch
from
September 30, 2026 07:31
b6a0581 to
77a92e7
Compare
mkouba
reviewed
Oct 1, 2026
manovotn
force-pushed
the
fix-synthetic-bean-priorities
branch
from
October 1, 2026 13:48
77a92e7 to
05274e0
Compare
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.
Fixes #3541
The idea is to change
Itemto be able to accommodate both, standard and synth beans into existing views.Synth. beans cannot be keyed based on bean class alone - you can easily register several beans with the same bean class.