Skip to content

Conversation

zepfred
Copy link
Contributor

@zepfred zepfred commented Sep 25, 2025

No description provided.

@zepfred
Copy link
Contributor Author

zepfred commented Sep 25, 2025

@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.

Copy link
Collaborator

@triceo triceo left a 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.


/**
* Creates a weight to decide the order of a collections of selections
* (a selection is a {@link PlanningEntity}, a planningValue, a {@link Move} or a {@link Selector}).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where do we weight selectors?
(And if selectors are not public API, should this be mentioning them?)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sorter is created by the WeightFactorySelectionSorter, which is utilized by ValueSelectorFactory and EntitySelectorFactory when creating the sorter nodes SortingValueSelector and SortingEntitySelector, respectively.

Comment on lines +66 to +67
* For example: sorting 3 computers on strength based on their RAM capacity:
* Computer B (1GB RAM), Computer A (2GB RAM), Computer C (7GB RAM),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a typical use for a list variable, is it?
Let's do VRP instead.

@zepfred
Copy link
Contributor Author

zepfred commented Sep 26, 2025

Finally, the change needs to show up in the upgrade recipe in our docs.

I have included a recipe for automatic migration to the new interface. Do we need to add anything to our docs?

Copy link

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