langgenius/dify

[Chore/Refactor] no-unstable-context-value

Open

#25278 opened on Sep 5, 2025

View on GitHub
 (4 comments) (1 reaction) (1 assignee)TypeScript (141,412 stars) (22,210 forks)batch import
good first issuerefactor🙏 help wanted

Description

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactoring, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Description

Prevents non-stable values (i.e. object literals) from being used as a value for Context.Provider.

React will re-render all consumers of a context whenever the context value changes, and if the value is not stable, this can lead to unnecessary re-renders.

Motivation

No response

Additional Context

https://eslint-react.xyz/docs/rules/no-unstable-context-value

Contributor guide

Tech stack
typescriptreact
Domain
frontend
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
React contextESLint basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Research the eslint plugin react x rule 'no unstable context value' from the provided link. Then, add the rule to the project's ESLint configuration (likely .eslintrc.js or eslint.config.js). Finally, run the linter and fix any reported violations across the codebase, ensuring that context values are stable (e.g., memoized).