This is something I miss from my prestans days, we have a feature we called attribute_filters it essentially allowed us toggle the visibility of fields in responses. What this allowed is to use the same model for different use cases e.g:
- List of users in the master view only needs,
id, name, email
- Clicking a user then loads the entire user including children model (this is the heavy weight use case)
Pydantic has the idea of excluding keys when it serializes content.
Explore and document:
- if this is possible using the FastAPI + pydantic toolset
- is this an OK thing to do according the OpenAPI specification
This is something I miss from my
prestansdays, we have a feature we calledattribute_filtersit essentially allowed us toggle the visibility of fields in responses. What this allowed is to use the same model for different use cases e.g:id,name,emailPydantic has the idea of excluding keys when it serializes content.
Explore and document: