Add MinSize and MaxSize Constraints to AnchorLayoutData #237
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 adds MinSize and MaxSize to AnchorLayoutData, making it easier to define size constraints directly within the layout data.
Why?
I was discussing this with a friend, and we both found the current way a bit unintuitive to set the minSize in the widget options. When trying to set min/max sizes, we instinctively looked for those properties in AnchorLayoutData, not in WidgetOpts. Having to set MinSize separately on the widget felt disconnected from the layout itself.
With this change, you can now define MinSize and MaxSize directly in AnchorLayoutData, making it more natural to work with:
Before (current way, still works):
After (my change, I think is look more intuitive):
With min size:

With min and max size:

Important:
The old way still works—this just adds an alternative way to set size constraints directly in the layout.
MaxSize didn’t exist before, so this also introduces a way to cap widget sizes inside AnchorLayout.
This should make it easier to reason about layout constraints while keeping everything backward-compatible.