Currently I have the given scenario:
I have one complexe model, which I want to publish on a suitable url endpoint.This works like a charm! Thanks for that!
Given the complexity of the model and the use case that I need only one attribute of the model sometimes, I defined a new url endpoint for the retrievement of just the attribute (with help of the only=[”attribute_name"])
So after this the results of endpoints "localhost/api/users" and localhost/api/user_email_validations" randomly switch from either all attributes or just the defined email_validated.
Is the usage with multiple endpoints for one SQLAlchemy model not wanted? Or did I miss something?
Thank in advance and thanks for the package anyway!
Currently I have the given scenario: I have one complexe model, which I want to publish on a suitable url endpoint.This works like a charm! Thanks for that!
Given the complexity of the model and the use case that I need only one attribute of the model sometimes, I defined a new url endpoint for the retrievement of just the attribute (with help of the only=[”attribute_name"])
Route for the overall model
Route for the one attribute only model
So after this the results of endpoints "localhost/api/users" and localhost/api/user_email_validations" randomly switch from either all attributes or just the defined email_validated.
Is the usage with multiple endpoints for one SQLAlchemy model not wanted? Or did I miss something?
Thank in advance and thanks for the package anyway!