you-might-not-need-an-effect

Arguments:

scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
fix: whether to apply fixes (default: true). Set to false to only propose changes.

Steps:

https://markdown.new/https://react.dev/learn/you-might-not-need-an-effect If inaccessible: https://react.dev/learn/you-might-not-need-an-effect
Analyze the specified scope for useEffect anti-patterns
If fix=true, apply the fixes. If fix=false, propose the fixes without applying.
If you REALLY REALLY need to use useEffect, add a comment in the code explaining why it's necessary and link to the relevant section of the guidelines.
Remember, useEffect is a escape hatch. If you cannot find alternative solutions, it's a kind of your loser's choice. But always try to find alternatives first before resorting to useEffect.

Arguments:

scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
fix: whether to apply fixes (default: true). Set to false to only propose changes.

Steps:

https://markdown.new/https://react.dev/learn/you-might-not-need-an-effect If inaccessible: https://react.dev/learn/you-might-not-need-an-effect
Analyze the specified scope for useEffect anti-patterns
If fix=true, apply the fixes. If fix=false, propose the fixes without applying.
If you REALLY REALLY need to use useEffect, add a comment in the code explaining why it's necessary and link to the relevant section of the guidelines.
Remember, useEffect is a escape hatch. If you cannot find alternative solutions, it's a kind of your loser's choice. But always try to find alternatives first before resorting to useEffect.

About