-
Notifications
You must be signed in to change notification settings - Fork 102
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: Use Named Solver fields and method parameters to determine list …
…of solver names in Quarkus (#1308) If a user is using named solvers, they should have `@Named` annotated fields or method parameters corresponding to the name solver. If they don't have such fields, said named solvers are not accessible anyways. Thus, Set(Named injected Solver types) = Set(accessible Solver names). So instead of using the keys of the SolverBuildTimeConfig as the set of solver names, we can use Set(Named injected Solver types) instead. This removes the need to include runtime properties in SolverBuildTimeConfig, since the map keys are no longer used to determine names. As a consequence, there is a behaviour change in the very contrived case of "exactly one named solver in properties (no default), no Named annotations, injected default solver". Since there was no Named annotations, the (empty) default solver properties will be checked instead of the single named solver properties. I consider the old behaviour to be a bug (named properties should not affect default properties), but the tests expect that behaviour.
- Loading branch information
1 parent
4316a5e
commit d3ae68f
Showing
19 changed files
with
407 additions
and
100 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.