mirror of
https://github.com/PrefectHQ/fastmcp.git
synced 2026-08-21 13:04:18 +02:00
Clarify why unresolved hints fall back to the raw annotation
🤖 Generated with Claude Code Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BAKNJthovhc5VSi4MTiZUe
This commit is contained in:
parent
2c7764b769
commit
f790c31c82
1 changed files with 3 additions and 2 deletions
|
|
@ -580,8 +580,9 @@ class FunctionResourceTemplate(ResourceTemplate):
|
|||
try:
|
||||
hints = _resolve_param_hints(fn)
|
||||
except NameError:
|
||||
# An annotation naming something we can't import here is not
|
||||
# worth failing registration over; fall back to the raw form.
|
||||
# Pydantic resolves annotations against namespaces this doesn't
|
||||
# see, so a name we can't resolve may still be valid. Fall back
|
||||
# to the raw form rather than failing a working registration.
|
||||
hints = {}
|
||||
|
||||
exploded = {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue