-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
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
no-access-state-in-setstate
throws on violations
#1559
Comments
That link is a 404. Could you perhaps paste the source in the issue or produce another link if it is too long? |
Sorry, didn't notice it was private repo. I removed everything that weren't triggering var SearchForm = createReactClass({
render: function () {
return (
<div>
{(function () {
if (this.state.prompt) {
return <div>{this.state.prompt}</div>
}
}).call(this)}
</div>
);
}
}); Looks like IIFE is the issue, changing {
this.state.prompt
? <div>{this.state.prompt}</div>
: null
} IDK if this is too "edge-casey" to fix compared to amount of work required, maybe mention in docs then? |
wow, i'd never expect to see an IIFE ever again in a world with modules :-) interesting find! |
@yannickcr do you plan to release a new version soon with this fix ? |
I'm getting this issue in |
@saiichihashimoto could you file a new issue with the code that’s causing the crash, along with the stack trace? |
@saiichihashimoto maybe you got #1657? |
v7.6.1 is released; please file a new issue if there's still problems :-) |
First of all, thank you everyone, who works on this project, it proved quite useful to me and I am really grateful! ❤️
Now, the problem is that
no-access-state-in-setstate
rule dies for me when violated. I have versions and stack, but not really sure if any other details are need, please let me know.Thanks for your help.
Versions:
Stacktrace:
The text was updated successfully, but these errors were encountered: