fixes possible override of uniqueMember by autodetection #15604
Merged
+17
−13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
desired or the initial value
was not set (as far as we knew)
It changes behaviour a bit:
uniqueMemberis not so common, and neither is not hitting "count groups". Imho, only impact for auto-installations were the attribute is not set specifically.I would say it is still OK to backport… more to the rules is to keep for 17 only though. The impact is small and rather beneficial.
What's left