Infer superview & return (constraints, views) - #19
Open
BrianKenny wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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 PS does 2 things. It lets regular view nodes opt into the inferred superview logic that's currently used for ghost views, in the case where they don't have a superview when constraints are created. This often gets rid of the need to ad subviews explicitly. Second, all the capture list operators go from returning just the constraints to returning a tuple of the constraints and the views. I've been converting all my spacerview code to mortarVFL, and almost every case we have something like
It only saves 2 lines, but one of those is re-writing the array in a different form, which is tedious and error prone.