langgenius/dify

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

Open

#25 193 ouverte le 5 sept. 2025

Voir sur GitHub
 (6 commentaires) (1 réaction) (0 assignés)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

Guide contributeur

Stack technique
typescriptreact
Domaine
frontend
Type d'issue
refactor
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-3 hours
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
fresh
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
clear
Prérequis
Understanding of React hooksFamiliarity with useContextBasic TypeScript knowledge
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
70
Direction de recherche
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.