Ensure action output models are models #239
Merged
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.
This uses
wrap_plain_types_in_rootmodelso thatActionDescriptor.output_modelis always a subclass ofpydantic.BaseModel. This brings its behaviour in line with that oflt.property(where we differentiate between thevalue_typeand itsmodel, with the latter always being aBaseModelsubclass).This fixes a bug that was ignoring annotations on action return types, identified in #231. There's an explanation there of what I believe is going on. When the specific invocation model is converted to a generic one by FastAPI, it preserves the value (and type) of each field but not annotations. Using a
RootModelinstead of an annotated type effectively bakes in any annotation as part of the class, and so it gets preserved and serialises correctly.I had thought the fix was more involved and would require separate endpoints for invocations of each action. I think this fix is much neater.