eslint-custom-guidelines

To enforce ESLint disable comments, apply a structured rule that only allows overrides for specific rules like 'state-management/prefer-state-architecture' with explicit justification. This approach supports React TypeScript projects using useState and common lint configurations.

Use an ESLint disable comment for state management warnings only when explicitly justified for specific scenarios like ephemeral UI state, form validation, or local loading indicators. You must document the reason in the codebase to maintain code quality.

The 'state-management/prefer-state-architecture' ESLint rule is a structured guideline for state usage in React TypeScript projects. It is needed when determining whether local useState should be replaced by React Query or Zustand for non-local UI state.

Yes, this ESLint configuration approach works with React Query and Zustand. It provides state-management guidelines that explicitly prefer using these libraries for non-local UI state instead of relying on local useState hooks and disabling lint rules.

To validate lint status after applying ESLint disable comments and fixes, run 'yarn checks' in your project. This command ensures your lint outcomes remain predictable and verifies that all overrides are correctly documented and applied.

The limitation of using ESLint disable comments is that they are only permitted when explicitly justified for specific rules. Unsafe overrides are restricted to maintain code quality, requiring documentation for scenarios like ephemeral UI state or form validation.