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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose
minreducedwidth
andminreducedheight
to API #6307Expose
minreducedwidth
andminreducedheight
to API #6307Changes from 4 commits
aeaba5c
f826ef7
bb2ca73
1c7cc49
61807ba
d692c7e
7fc8514
c53e084
2fc928d
0effd0f
6a43af4
21f71e6
93b05d3
0fff290
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alexcjohnson Is there a better place to put these new attributes in?
It looks like these are related to
automargin
notmargin
itself.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@archmoj and I discussed this a bit earlier today, and I think the conclusion we came to was: because
margin.autoexpand
controls whether or not these attributes are even relevant, (1) they should stay here, so they're in the same container asautoexpand
, and (2) ifautoexpand
isfalse
we shouldn't even coerce these two new ones. (The general rule is, if an attribute doesn't do anything because of the value of some other attribute(s), it should not be coerced)The only question is whether it's really true that these attributes are irrelevant when
autoexpand=false
. According to its description this would disable automargin from "Legends, colorbars, updatemenus, sliders, axis rangeselector and rangeslider" but what ifxaxis.automargin=true
? Maybe then the margins can still be pushed even ifmargin.autoexpand=false
? That needs to be tested before we make coercion conditional onmargin.autoexpand
- but even if that's the case I think it makes sense to leave these attributes where they are.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed in 93b05d3.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, @archmoj and I looked into the source code and decided that these attributes would be best placed at the top level of layout parameters as they could be related to
autoexpand
as well (and I think logically make sense alongsideheight
andwidth
).