langgenius/dify

[Refactor/Chore] migrate to TypedDict

Open

#32 863 ouverte le 2 mars 2026

Voir sur GitHub
 (46 commentaires) (1 réaction) (4 assignés)TypeScript (141 412 stars) (22 210 forks)batch import
good first issue🙏 help wanted

Description

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactors or chores; 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

now codebase is full of : dict, -> dict -> Mapping : Mapping

we should use TypedDict whenever possible.

@dosu give me a list of file need to change.

and show how to change.

Motivation

No response

Additional Context

No response

Guide contributeur

Stack technique
python
Domaine
backend
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.
over 1 week
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
blocked
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
mostly clear
Prérequis
PythonType hintsTypedDict
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
25
Direction de recherche
The issue is to migrate all plain `dict`, `Mapping` type hints to TypedDict across the Python codebase. The issue has 4 assignees and 46 comments, indicating it is actively claimed and discussed. A first time contributor should instead look for issues with no assignees or a 'help wanted' label. The migration involves identifying function signatures and variable annotations using `dict` or `Mapping` and replacing them with specific TypedDict classes. Example files to examine are in core modules; see the issue for discussion.