Document label and enum alignment values for EDGE components#444
Open
simonhamp wants to merge 1 commit into
Open
Document label and enum alignment values for EDGE components#444simonhamp wants to merge 1 commit into
simonhamp wants to merge 1 commit into
Conversation
simonhamp
marked this pull request as ready for review
July 24, 2026 12:37
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.
What
Updates the mobile v4 EDGE component docs to reflect that alignment attributes now accept a readable label, a backing enum, or the raw integer — all three resolve to the same native value.
Native\Mobile\Edge\Enumsenums (AlignItems,AlignSelf,JustifyContent,TextAlign) used fluently.text-alignasleft/center/right(label,TextAligncase, or0/1/2) and updates thetextAlign()signature toint|string|TextAlign.AlignItems::Centerinstead of the magic number1.align-items="center"instead of:align-items="1".Why
The previous docs only showed opaque integer values (
:align-items="1",:justify-content="3"), which are hard to read and easy to get wrong. Surfacing the label and enum options makes the examples self-documenting while keeping the integer mapping available for reference.Docs-only change; no application code touched.