forbid-prop-types: propWrapperFunctions does not follow identifiers
#1352
Labels
Comments
|
@yannickcr 5ad93b4 is a crasher, so it'd be good to cut a quick patch release with that in it :-) |
|
I’ll take a look at fixing this bug.
…On Wed, Aug 9, 2017 at 20:31, Jordan Harband ***@***.***> wrote:
@yannickcr <https://github.com/yannickcr> 5ad93b4
<5ad93b4>
is a crasher, so it'd be good to cut a quick patch release with that in it
:-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1352 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA5hFq9mN-g8sY8fqCfOGszGjuo_njcAks5sWnmRgaJpZM4Oy5OV>
.
|
dustinsoftware
pushed a commit
to dustinsoftware/eslint-plugin-react
that referenced
this issue
Aug 11, 2017
This fixes incorrect behavior when propTypes were stored in a variable and then referenced later. jsx-eslint#1352
dustinsoftware
pushed a commit
to dustinsoftware/eslint-plugin-react
that referenced
this issue
Aug 11, 2017
This fixes incorrect behavior when propTypes were stored in a variable and then referenced later. jsx-eslint#1352
dustinsoftware
pushed a commit
to dustinsoftware/eslint-plugin-react
that referenced
this issue
Aug 11, 2017
This fixes incorrect behavior when propTypes were stored in a variable and then referenced later. jsx-eslint#1352
dustinsoftware
pushed a commit
to dustinsoftware/eslint-plugin-react
that referenced
this issue
Aug 11, 2017
This fixes incorrect behavior when propTypes were stored in a variable and then referenced later. jsx-eslint#1352
|
@ljharb yep, I'll do a patch release shortly. |
This was referenced Sep 22, 2018
This was referenced Oct 25, 2018
1 task
1 task
1 task
This was referenced Jan 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I fixed a crash from #1253 in 5ad93b4.
However, see the TODO - the rule (prop-types also) is not following the identifier reference when it's not inline. It should.
cc @dustinsoftware
The text was updated successfully, but these errors were encountered: