Add rule S6756 (no-access-state-in-setstate): \"setState\" should use a callback when referencing the previous state
#4154
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…se a callback when referencing the previous state
yassin-kammoun-sonarsource
force-pushed
the
i4132
branch
from
b8fcdbf
to
146c6c7
Compare
yassin-kammoun-sonarsource
changed the title
no-access-state-in-setstate): React state updates should not depend on stale statesno-access-state-in-setstate): \"setState\" should use a callback when referencing the previous state
alex-sonar
approved these changes
Sep 11, 2023
|
SonarQube Quality Gate
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #4132