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 #4352 and fix #4977 and entails a visual change.
To recap the issue: whether the
legend.spacing.{x/y}
was adhered to between keys was strangely dependent on theguide_legend(byrow = ...)
setting. This made setting vertical spacing very unintuitive. With guides having been recently rewritten, there is no better time to justify visual changes.This PR currently does three things:
legend.spacing.{x/y}
inherits from thelegend.spacing
theme setting.byrow
on spacing is nullified.There are a few things I'd like some input on:
legend.spacing.text
theme setting? Note that for finetuning text-to-something spacing, themargin
argument is available.This PR breaks a bunch of visual tests, so I've not committed these changes yet in anticipation of further changes.
A visual example of the new spacing:
Removing the spacing brings the plot closer to previous plots.
Created on 2023-04-24 with reprex v2.0.2