Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use config ordinal to determine which config style to use when injecting a list, between comma-separated and indexed #1301

Merged
merged 1 commit into from
Feb 1, 2025

Conversation

radcortez
Copy link
Member

@radcortez radcortez commented Feb 1, 2025

With #1202, we changed the priority order when selecting between a comma-separated value or indexed name format to populate a Collection. We did this to make things consistent because the comma-separated format only works for plain types, and if we require to configure a list group, it can only be expressed with the indexed format.

This was a breaking change that was not well received, so in #1266, we modified the APIs to take into account the source ordinal, meaning that we use the ordinal of the source to determine which to use, if both are available.

This PR adds the same behaviour to the injection producer.

…ing a list, between comma-separated and indexed
@radcortez radcortez merged commit 2e5ca14 into smallrye:main Feb 1, 2025
6 checks passed
@github-actions github-actions bot added this to the 3.11.2 milestone Feb 1, 2025
@dmlloyd
Copy link
Contributor

dmlloyd commented Feb 3, 2025

Can you explain this heuristic? There is no doc change and it's not clear what's going on here.

@radcortez
Copy link
Member Author

Added a description. Sorry for not being transparent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants