Document type annotation principles for FastAPI dependency injection #1
+158
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The problem statement asks how to properly annotate return types in dependency functions:
ChatService()vsChatService, and requests a principle-based explanation.Changes
Added comprehensive documentation section "依赖注入的类型注解原理" to FastAPI框架.md covering:
ChatService(type) notChatService()(call expression) in type annotationsAnnotatedmechanics: First parameter is the type for type checkers, second is FastAPI metadata (Depends)Example
Type annotations always use types (classes), never call expressions. The dependency system handles instantiation and injection at runtime.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.