Allow recursively nested tokens in attributes #807
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.
If you have a component that you want to take in an attribute of a token list, like
class
, and you want your interface to be polymorphic like an element method's attributes would be, you currently need to type check the provided attribute and handle it manually.Before this PR, the above example will break if the person using the Card component tries to supply an array of classes, because
Array
is not a valid token type for__nested_tokens__
.Now if an array is passed, it will also have
__nested_tokens__
called on it.