You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, @LeiYangGH, tbh I didn't know about fastapi-crudrouter until after I had almost released fastcrud, so it didn't inspire my design decisisons.
Since the EndpointCreator was - for me - a natural evolution of the FastCRUD class, I used the same urls for the endpoints as I used for the methods names.
Indeed I think the way fastapi-crudrouter does it is better, which is why @JakNowy fixed this here, for now we added a warning, but in 0.15 it will become the standard way.
You can see the warning in the docs here or when you don't pass endpoint names when using crud_router or EndpointCreator.
I tried both fastapi-crudrouter and
fastcrud
, and yes,fastcrud
is actively maintained and support latest libraries versions, thank you!but comparing the auto generated(default) api urls, I'm wondering why
fastcrud
not reuse the originalfastapi-crudrouter
api schema.for example,
get all:
fastapi-crudrouter
model
fastcrud
model/get_multi
create
fastapi-crudrouter
model
fastcrud
model/create
though url patterns can be customized, personally I think
fastapi-crudrouter
is more elegant(at least it requires less typing ^_^).So could you add document section on the design thoughts?
The text was updated successfully, but these errors were encountered: