langgenius/dify

better orm typing

Open

#22,652 opened on Jul 18, 2025

View on GitHub
 (9 comments) (2 reactions) (1 assignee)TypeScript (141,412 stars) (22,210 forks)batch import
good first issue💪 enhancement

Description

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

continue of #22626

now all the orm has Any as typing, but require more work to let typing work.

split into mutliple issues, since each step may cause other typing bugs.

2. Additional context or comments

now we are here: https://docs.sqlalchemy.org/en/20/changelog/whatsnew_20.html#step-three-apply-exact-python-types-as-needed-using-orm-mapped

example: #23322

3. Can you help us with this feature?

  • I am interested in contributing to this feature.

Contributor guide

Tech stack
pythonsqlpostgresql
Domain
backenddatabase
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-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Python typing basicsSQLAlchemy ORM experience
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
This issue is a continuation of #22626 and aims to improve ORM typing by applying exact Python types as described in SQLAlchemy 2.0 migration step three (https://docs.sqlalchemy.org/en/20/changelog/whatsnew 20.html#step three apply exact python types as needed using orm mapped). The existing ORM models currently use `Any` types. The work involves updating models to use proper types, following the pattern in example #23322. The issue may be split into multiple smaller tasks. The assignee has commented (check issue comments) and there is no open PR yet. First time contributors should review the referenced PR #23322 and the SQLAlchemy documentation to understand the required changes.