At some point, #2239 is going to be merged and remove CollectionContainsConstraint. The only breaking change should be where anyone is explicitly using the code new CollectionContainsConstraint() - all the other methods will be changed internally to use a SomeItemsConstraint instead.
I think it would be good if we can obsolete the CollectionContainsConstraint constructor in v3.8, and then merge the actual constraint removal in v3.9. It should only be the constructor itself that is obsoleted - any other public methods which make use of the class will be refactored. The obsoletion message should state that SomeItemsConstraint is the appropriate replacement.
At some point, #2239 is going to be merged and remove CollectionContainsConstraint. The only breaking change should be where anyone is explicitly using the code
new CollectionContainsConstraint()- all the other methods will be changed internally to use a SomeItemsConstraint instead.I think it would be good if we can obsolete the CollectionContainsConstraint constructor in v3.8, and then merge the actual constraint removal in v3.9. It should only be the constructor itself that is obsoleted - any other public methods which make use of the class will be refactored. The obsoletion message should state that
SomeItemsConstraintis the appropriate replacement.