langgenius/dify

[Chore/Refactor] 'use' is preferred over 'useContext' because it is more flexible

Open

#25193 opened on Sep 5, 2025

View on GitHub
 (6 comments) (1 reaction) (0 assignees)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

use use

Motivation

'use' is preferred over 'useContext' because it is more flexible

Additional Context

https://react.dev/reference/react/use#reading-context-with-use

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.
3
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of React hooksFamiliarity with useContextBasic TypeScript knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Look for all usages of `useContext` in the codebase, particularly in component files. Replace each with the `use` hook, following the pattern described in the React docs (https://react.dev/reference/react/use#reading context with use). Ensure the context object is passed as argument to `use`. After replacement, verify that the application still compiles and that context values are correctly consumed by running the existing test suite and performing manual smoke tests on affected UI areas.