[QUESTION] Support both /users/{user_id} and /users/_bulk

I have /users API that supports PUT and GET for /users/{user_id}. Now I want to introduce a bulk API to update several users at once. I thought about introducing /users/_bulk endpoint for PUT operations - we don’t allow _ in our IDs hence there is no URL collision.

However when trying to implement it in FastAPI they do collide and /users/_bulk gets routed to /users/{user_id}.

In our old system we use aiohttp which stores routes just a a list. Hence, to solve the above “collision” we just sort routes as

paths = sorted(paths, key=lambda x: x.count("{"))

which effectively pushes more vague, pattern routes down the list.

Do you think it will be a valid request for FastAPI to do the same?

[haizaar]

/CC @motinani, @worroc

Hi @tiangolo, I moved to new place where I’m not involved with FastAPI anymore. I’d like to once again express my deep gratitude to you for creating this amazing project!

[haizaar]

Found the reason why it seemed to work regardless of the order - by accident I defined bulk endpoint as /users/_bulk/ with trailing / while /users/{user_id} without.

Such a waste of everyone’s time 😐

Thank you @euri10 and @tiangolo for looking into this.