langgenius/dify

api.model to BaseModel

Open

#28015 opened on Nov 9, 2025

View on GitHub
 (20 comments) (1 reaction) (1 assignee)TypeScript (141,412 stars) (22,210 forks)batch import
good first issue🐞 bug🙏 help wanted

Description

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, 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.

Dify version

master

Cloud or Self Hosted

Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

fields\.[A-Z]

✔️ Expected Behavior

no more fields

❌ Actual Behavior

no the same

Contributor guide

Tech stack
typescript
Domain
backend
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
This issue appears to be about renaming or replacing `api.model` with `BaseModel` in the codebase, possibly to unify model naming. The steps to reproduce include a regex `fields\.[A Z]` suggesting the need to eliminate such patterns. The body and expected behavior are unclear; there are 20 comments that likely contain more context. A contributor should first review the comments to understand the exact scope and expected changes. Then, search the codebase for `api.model` usages and instances of `fields.[A Z]` patterns to determine the refactoring needed. It may be necessary to contact the maintainer for clarification on the desired outcome.