langgenius/dify

api.model to BaseModel

Open

#28.015 aberto em 9 de nov. de 2025

Ver no 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

Guia do colaborador

Pilha de tecnologia
typescript
Domain
backend
Tipo Issue
refactor
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-3 hours
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
needs maintainer response
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
unclear
Prerequisites
None
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
30
Direção de pesquisa
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.