Routing improvements

[vytas7]

Improved routing is undeniably a popular topic among feature requests from the community.
Let us try to start a discussion here on Discussions 👋

Tracked issues

• Explore object-based routing Explore object-based routing #319
• Advanced filters such as matching multiple path segments etc Add support for filters in route templates #423
• Routing all paths to one handler function (editor's note: potential duplication of the sink feature) Routing all paths to one handler function #648
• Conflicting URI templates Conflicting URI templates #663
• Add support for query string parameters in route templates Add support for query string parameters in route templates #838
• Cascade blueprints a-la Flask How about cascade blueprint like in flask #855
• Calling API from inside Resource handler (loosely related) Calling API from inside Resource handler? #1228
• Inter-resource delegation, similar to Flask's url_for() Add a helper to generate the URL for a resource #1264
• Allow different parameter names for the same segment across routes Why can't we define routes with different field expression parameter names for same routes? #1471
• Use pattern hints from converters Use pattern hints from converters when matching fields #1567
• Include responder in middleware process_resource Include responder in middleware process_resource #1629
• (Probably a couple more)

Workarounds

• Using sinks to match any arbitrary path regex.
• Rewriting request path in middleware before routing (think internal redirect) in order to match other routes or sinks.
• Implementing a custom router.
• Anything else?

We would love to hear which potential routing improvements are the most important to You, the framework user.
Feel free to share ideas for improvement, examples from your use cases, and workarounds you found!

[vytas7]

Reposting from Gitter

Morteza NourelahiAlamdari @mortymacs 10:50
I was trying to have repetitive routes in Falcon and I didn't find anything related to it. For example something like <parent>/folders/<child>/folders/<parent>/folders/<child>/....
I have an idea in my head and I want to know if we don't have this feature in Falcon, I can start implementing it. It's useful when we want to address nested patterns. Is there any better approach that exists for it?

[vytas7]

More from Gitter

Morteza NourelahiAlamdari @mortymacs
Is it possible to get a route "suffix" in middleware? like in process_resource?

This is apparently already tracked as #1629 (added to the introductory list too).

[adsahay]

I'd like to vote for this - either object based or flask-blueprint like routing. It helps for larger projects. This could also be an add-on as you would want to keep everything backward compatible. If I get some direction I am happy to attempt a proof of concept.

[B1gG]

Hi guys,
I am playing with add_static_route to serve some static files while developing as in production it should be captured by nginx.
But I was wondering should be there a way to skip the middleware processing for static routes?
at the moment I keep repeating this thing in each middleware methods:

        if '/static/images' in req.path:
            return

[kgriffs]

Is there an existing issue we can link for implementing something along the lines of url_for for Falcon?

[vytas7]

Yes. there is: #1264 (added to the list).

[kgriffs]

Thanks for tracking that down. I updated the title/description for the issue.

[aprilahijriyan]

Hi @vytas7 , I just created a routing sub application on my project maybe it could be part of falcon?

To add a sub-application:

https://github.com/aprilahijriyan/falca/blob/develop/falca/scaffold.py#L105-L121

Main logic:

WSGI:
https://github.com/aprilahijriyan/falca/blob/develop/falca/app.py#L17-L21

ASGI:
https://github.com/aprilahijriyan/falca/blob/develop/falca/app.py#L34-L38

[maxking]

We've been using a Object router in Mailman 3 that we have a custom implementation.

It could use more documentation, but in terms of usage, we define a Top level resource Root here and then we use a @child decorator to define a sub-resource. Each method gets passed a list of URL segments to make decision on routing further in the depth.

I thought I'd share it here as I came across this discussion form Gitter.

This is what is mentioned in #319

[vytas7]

Thanks for sharing @maxking!