dep inject in current flask

Description

This issue does not include a description.

Contributor guide

Tech stack

pythonflasktypescript

Domain

backendapi

Issue type

feature

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.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

needs investigation

Prerequisites

Basic Flask knowledgeDependency injection concepts

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

30

Research direction

This issue proposes adding dependency injection to the current Flask implementation in Dify. No detailed description is provided, so the first step is to clarify the scope by reviewing the Flask related code in the repository, particularly in the Python backend. Look at existing tests or configuration files for Flask routes and services. Check the repository's issue tracker for any related discussions. Then, propose a design for a simple dependency injection mechanism, perhaps using Flask's current extension system or a lightweight library like 'injector' or 'python dependency injector'. The implementation should be low impact and maintain backward compatibility.