Warn about simultaneous use of mapped and static aesthetics #6743
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.
This PR aims to fix #6429.
Instead of improving the 'no shared levels' warning as implied by the issue, this PR separately warns about the simulatenous use of an aesthetic in
mappingand as a fixed aesthetic.We only do this when this occurs within a layer. If local fixed aesthetics contradict the global mapping, this is not a warning:
Created on 2025-11-12 with reprex v2.1.1
This is because people can intentionally deviate the local aesthetic from global mappings to exempt that aesthetic from
inherit.aes. In contrast, I don't think you can intentially have contradicting aesthetics in a single layer.