-
Notifications
You must be signed in to change notification settings - Fork 160
feat: enable sorting for CH with list variable #1833
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
base: main
Are you sure you want to change the base?
Conversation
@triceo I noticed other factories used by configurations and annotations that are not located in the public API. Maybe, we should handle that in a separate PR as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As always, the different selector combinations are causing me to ask questions - see inline.
Downstream tests are failing.
Also, please provide a migration recipe for the move of the interface to the public API; the uses of the old interface should be replaced by the new one.
Finally, the change needs to show up in the upgrade recipe in our docs.
core/src/main/java/ai/timefold/solver/core/api/domain/common/ComparatorFactory.java
Show resolved
Hide resolved
core/src/main/java/ai/timefold/solver/core/api/domain/common/ComparatorFactory.java
Show resolved
Hide resolved
core/src/main/java/ai/timefold/solver/core/api/domain/common/SorterWeightFactory.java
Outdated
Show resolved
Hide resolved
core/src/main/java/ai/timefold/solver/core/api/domain/variable/PlanningListVariable.java
Outdated
Show resolved
Hide resolved
...efold/solver/core/impl/heuristic/selector/common/decorator/SelectionSorterWeightFactory.java
Outdated
Show resolved
Hide resolved
...in/java/ai/timefold/solver/core/impl/heuristic/selector/list/DestinationSelectorFactory.java
Outdated
Show resolved
Hide resolved
...in/java/ai/timefold/solver/core/impl/heuristic/selector/list/DestinationSelectorFactory.java
Outdated
Show resolved
Hide resolved
89b3bd0
to
beebea8
Compare
I have included a recipe for automatic migration to the new interface. Do we need to add anything to our docs? |
beebea8
to
bd61abc
Compare
@triceo we include the property The property |
Yes, the old names should be deprecated. Code which uses them should still work, but the code which combines the old names and the new names should fail fast - it's either all the old names, or all the new names. Arguably |
We already have |
|
No description provided.