-
Notifications
You must be signed in to change notification settings - Fork 99
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
fix: Ruin and Recreate move reversion #1309
Conversation
032b070
to
0795c13
Compare
...in/java/ai/timefold/solver/core/impl/move/director/VariableChangeRecordingScoreDirector.java
Outdated
Show resolved
Hide resolved
...imefold/solver/core/impl/heuristic/selector/move/generic/list/ruin/ListRuinRecreateMove.java
Outdated
Show resolved
Hide resolved
85dd9d5
to
b1bd171
Compare
Quality Gate passedIssues Measures |
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.
I believe that the recorder situation can be simplified. The move should not really deal with what's recorded, and what's a custom change. The move should just say what it wants - it wants some changes to not be delegated.
...imefold/solver/core/impl/heuristic/selector/move/generic/list/ruin/ListRuinRecreateMove.java
Show resolved
Hide resolved
Fixed by #1320 |
No description provided.