You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the airbnb style guide, which enables the react/style-prop-object rule. For most use cases this is fine. However, I just started implementing react-intl. This exposes a <FormattedNumber> component which accepts a style prop. This triggers the react/style-prop-object rule.
I think it’s generally a bad practice to create props using such standarized names, but third party libraries might. I suggest adding an option to this rule, which defines an array of component names for which different style prop types are allowed.
I am using the airbnb style guide, which enables the
react/style-prop-object
rule. For most use cases this is fine. However, I just started implementingreact-intl
. This exposes a<FormattedNumber>
component which accepts astyle
prop. This triggers thereact/style-prop-object
rule.I think it’s generally a bad practice to create props using such standarized names, but third party libraries might. I suggest adding an option to this rule, which defines an array of component names for which different style prop types are allowed.
For example:
The text was updated successfully, but these errors were encountered: