Add custom attribute mapping feature #155
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.
I'm using this package with React Router. React Router has a
<NavLink>
component which has anactiveClassName
attribute, to be appended to itsclassName
when it's active.However, I think it's extreme ugly when I can use
styleName
everywhere except here.At first I want to extend the support to any attribute names ending with
styleName
/StyleName
, but at last I added thisattributeNames
option to allow customization of the transformation. Each key represents a source attribute name and the corresponding value represents the destination attribute name. I think this feature can make it more easily to deal with components with multiple states, or with multiplexxxClassName
attributes.The default value is
{ "styleName": "className" }
to keep backward compatibility, and the specified object will be merged with this default value unless it contains a different value forstyleName
.A very rare (maybe just non-exist) use case will be setting
styleName
to something else ornull
. It just means the transformation process is totally controllable.