Add future flag to preserve custom, default ring color opacity #8448
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.
Currently we apply the default ring opacity to any custom, default ring color even when it has an opacity specified explicitly. This default opacity is only used by the default ring color making the behavior even more confusing. Since this is not the most expected behavior we'll be changing this. Given that it's a backwards incompatible change we cannot do so until v4 (whenever that happens in the future).
To ease future migration we'll allow users to opt-in to this change earlier by using the new feature flag
future.respectDefaultRingColorOpacity
which preserves the default ring color the user specifies effectively as is.Fixes #7800