Support custom prop aliases API #171
Open
Conversation
This file contains 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
kettanaito
force-pushed
the
126-prop-alias-api
branch
from
3c9a60f
to
45fbcb0
Compare
kettanaito
force-pushed
the
126-prop-alias-api
branch
from
3f7a388
to
77d8c9a
Compare
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.
Change log
transformNumericto get rid of circular dependency fromLayoutGitHub
Motivation
Having custom prop aliases is something I constantly miss when developing using Atomic layout. Although it may contradict with the original nature of this library being responsible for spacial distribution only, it's the end developer's responsibility to separate concerns. I believe custom prop aliases may help more than they would harm.
Roadmap