-
Notifications
You must be signed in to change notification settings - Fork 84
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
Feat: Improve error message when @PlanningListVariable is used alongside a @PlanningVariable on different classes #683
Comments
If the
|
@Christopher-Chianelli That's an important distinction. We are absolutely sure we do not support combining list variables and basic variables on the same entity. But are we so sure we don't support it on two different entity classes? |
I am pretty sure there are no tests for
|
The docs is ambiguous too - does "coexistence" mean "in the same solution" or "in the same entity class"? IMO this needs to be tested to know for sure. If we can reconfigure the selector manually to two selectors, one for each entity, and it still blows up, then it's clear - we do not support this use case. (I think that this is the more likely outcome, I'm just not 100.0 % sure.) |
Well, "Construction Heuristic phase with a list variable does not support moveSelectorConfigList configuration. Remove the moveSelectorConfigList ([UnionMoveSelectorConfig(null)]) from the config.", so it is impossible to configure the selector. |
Is your feature request related to a problem? Please describe.
Currently, if you use a
@PlanningVariable
and a@PlanningListVariable
on different classes, the following exception occurs:Describe the solution you'd like
Ideally, the error message should improve by telling the user that
@PlanningListVariable
cannot be used with@PlanningVariable
currently:Describe alternatives you've considered
This issue will become stale once PlanningListVariable supports co-existing with other PlanningVariable(s)
Additional context
https://stackoverflow.com/q/78102453/9698517
The text was updated successfully, but these errors were encountered: