Improve EdgesConstrainableProxy
API ↔️
#247
Merged
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.
Checklist
master
Motivation and Context
Until now, it wasn't possible to define edges constraints using a
NSDirectionalEdgeInsets
value, requiring one to convert them toUIEdgeInsets
.Additionally, the
EdgesConstrainableProxy.edges()
API only received a singlerelation
andpriority
parameters for all edges, which is often not ideal in real scenarios. Some examples are:priority
and not othersrelation
needs to be inverted betweenleading
/trailing
ortop
/bottom
.To address the above, a new overload was added to
EdgesConstrainableProxy
that takes in aNSDirectionalEdgeInsets
instance, and new edge-specific relation/priority parameters were added.Changes
Description
Add a new
EdgesConstrainableProxy.edges
overload that receives aNSDirectionalEdgeInsets
instance instead of aUIEdgeInsets
.Allow tweaking
relation
andpriority
for each edge of aEdgesConstrainableProxy
.Create helpers to convert between
UIEdgesInsets
andNSDirectionalEdgesInsets
.