You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think you can already specify padding using the width aesthetic and the position_dodge(width) parameter. Is there an example that is inconvenient where padding would alleviate some gnarlyness?
Ah I see, I didn't think of this! No, I can't think of an example that could not be achieved by using that method.
Still though, conceptually, if position_dodge and position_dodge2 are intended to be the same other than the grouping variable thing, then they should have the same arguments? So, either add padding to position_dodge or deprecate it from position_dodge2 if not needed. Likewise for reverse.
So position_dodge2() needs a padding argument because it deals with variable-width data structures, whereas position_dodge() does not. For this reason, using width fixes the issue for position_dodge() but not position_dodge2().
The reverse argument has been added in #5932.
Just as this is sometimes useful in
position_dodge2
, it could be useful at times inposition_dodge
It would also be a way to have borders around dodged bars, and resolve issues with positioning noted in #5997
The text was updated successfully, but these errors were encountered: