langgenius/dify

add type annotation to api endpoints

Open

#36541 opened on May 23, 2026

View on GitHub
 (12 comments) (1 reaction) (0 assignees)TypeScript (141,412 stars) (22,210 forks)batch import
good first issue

Description

so we can easily do following migration.

rule: when find any

.route("/apps/<uuid:app_id>/messages/<uuid:message_id>")

begin with uuid: , type the parameter to UUID. begin with string:, type the parameter to str.

Contributor guide

Tech stack
pythonflask
Domain
backendapi
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Python type hintsFlask routing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue requires finding all Flask route decorators in the codebase that use `uuid:` or `string:` as parameter prefixes, such as `/<uuid:app id>`. For each such route, add type annotations to the function parameters (e.g., `app id: UUID`) and ensure the route converter is properly typed. Focus on API endpoint files, likely under `api/` directory. Check existing type hints in similar routes for consistency.