We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
See https://stackoverflow.com/questions/73954484/should-i-use-the-package-prop-types-or-pass-a-props-interface-to-react-component
Should it be applied conditionally only to Typescript projects though? That might require some new functionality in the plugin
The text was updated successfully, but these errors were encountered:
i wonder if it sits better with one of the react specific eslint plugins (e.g. one of the alternatives to eslint-plugin-react we probably list here)
since the rule could then be "if in typescript, assert that an interface is used, otherwise, assert prop-types is used" etc
Sorry, something went wrong.
Filed issues there to see what the maintainers of those libraries think about the idea:
prop-types
No branches or pull requests
See https://stackoverflow.com/questions/73954484/should-i-use-the-package-prop-types-or-pass-a-props-interface-to-react-component
Should it be applied conditionally only to Typescript projects though? That might require some new functionality in the plugin
The text was updated successfully, but these errors were encountered: