Allow controlling the layout bounds via the Environment #317
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kyleve
force-pushed
the
kve/allow-env-to-control-layout-bounds
branch
3 times, most recently
from
1e4ff46 to
da2f888
Compare
kyleve
force-pushed
the
kve/allow-env-to-control-layout-bounds
branch
from
da2f888 to
322952b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 does a couple things:
ListContentBounds, which can be shared across layouts; and now have a default provided by the environment. This will eventually allow Market to provide a default content bounds to implement its desired sizing and padding behaviour.ListSizingtoList.Measurement, to reflect that it is only used byList, and to better match the Blueprint terminology for measurement.