Made flex and flexChildren available again #2546
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.
Background
Our Stack implementation on POS still has some limitations when it comes to avoiding flex and
flexChildren
. For example, we don't have any way to implement JustifyItems right now which would let the buttons and other components stretch across the main axis, so we still needflexChildren
to accomplish this. As forflex
, we need to expose this property so that partners can tell theStack
to take the whole screen if they want. Ideally in the future we refactor our Screen implementation to be flex independent, but this will take time and work that we don't have the capacity for right now.Solution
Removes the deprecation warnings for flex and flexChildren. It also fixes up some documentation.
🎩
Checklist