langgenius/dify

[Chore/Refactor] remove ignore in pyright config

Open

#26412 opened on Sep 29, 2025

View on GitHub
 (8 comments) (1 reaction) (2 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

now pyright ignore some folders, fix the typing errors in them and let pyright check them.

Motivation

improve type check coverage.

Additional Context

No response

Contributor guide

Tech stack
pythontypescript
Domain
toolingdeveloper experience
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.
3-5 days
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.
clear
Prerequisites
Familiarity with Python type hintsBasic knowledge of pyright
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue asks to remove pyright ignore entries from the configuration file (likely pyproject.toml) and fix any resulting type errors. Start by locating the pyright configuration in the repository root. Then, run pyright to identify errors after removing ignore entries. Fix each error by adding proper type annotations or correcting types. Check the issue comments for any progress from assignees (2 assigned). The pull request list is empty, so this work is likely unstarted. The repository's Python code is probably in backend directories; focus on those.