18 ms·
for someone that comes primarily from a .net background. This looks fantastic! Just one thing that I tried to find more information about is: are you suppose t
by asabla 2y ago
for someone that comes primarily from a .net background. This looks fantastic!
Just one thing that I tried to find more information about is: are you suppose to rely on the prefix for specifying api version?
Disclaimer:
I'm on a phone while writing this, so I just might have missed something obvious
other then that, kudos for releasing this package!
- mr_Fatalyst 2y agoIn the examples, I used prefixes to demonstrate API versioning, but you're not limited to this approach. Prefixes can be used for general route structuring as well (like grouping entities, etc.), not just for versioning. Personally, I prefer using router composition for flexible route organization. You can see a clear example of this with Flask here: https://github.com/mr-fatalyst/fastopenapi/tree/master/examples/flask https://github.com/mr-fatalyst/fastopenapi/tree/master/examp... In this example, routes are split into routers by entities, which are then grouped into an api_v1 router, and finally, this api_v1 router is added to the main router.