langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 03:55:25 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

better orm typing #15505

New Issue
Open
opened 2026-02-21 19:22:02 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:22:02 -05:00
Owner
Copy Link
Copy Source

Originally created by @asukaminato0721 on GitHub (Jul 18, 2025).

Originally assigned to: @asukaminato0721 on GitHub.

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.
Originally created by @asukaminato0721 on GitHub (Jul 18, 2025). Originally assigned to: @asukaminato0721 on GitHub. ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 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? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancementgood first issue labels 2026-02-21 19:22:02 -05:00
yindo commented 2026-02-21 19:22:03 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 25, 2025):

Hi, @asukaminato0721. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary

  • You requested enhanced ORM typing to replace the current use of Any for more precise type annotations.
  • The work is planned to be broken into smaller issues to better manage typing bugs.
  • You referenced SQLAlchemy 2.0's typing approach as a model for improvement.
  • No further activity or updates have been recorded on this issue so far.

Next Steps

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 25, 2025): Hi, @asukaminato0721. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary** - You requested enhanced ORM typing to replace the current use of `Any` for more precise type annotations. - The work is planned to be broken into smaller issues to better manage typing bugs. - You referenced SQLAlchemy 2.0's typing approach as a model for improvement. - No further activity or updates have been recorded on this issue so far. **Next Steps** - Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:22:03 -05:00
Author
Owner
Copy Link
Copy Source

@asukaminato0721 commented on GitHub (Aug 25, 2025):

yet another good first issue.

@asukaminato0721 commented on GitHub (Aug 25, 2025): yet another good first issue.
yindo commented 2026-02-21 19:22:03 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 25, 2025):

@crazywoola The user has confirmed this issue is still relevant and mentioned it as "yet another good first issue." Could you please assist with this ORM typing enhancement?

@dosubot[bot] commented on GitHub (Aug 25, 2025): @crazywoola The user has confirmed this issue is still relevant and mentioned it as "yet another good first issue." Could you please assist with this ORM typing enhancement?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label good first issue 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#15505
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?