> That’s actually what I ended up doing, but it isn’t something you can rely on > in a big project… > > Why not?
Because you’d have to document very clearly the fact that some specific rules need to be organized in a precise order among the list. If you have hundreds of URLs managed in your routes.py and if 10 of them need to be organized in specific orders then if you want to add an URL you need a very clear view of exactly where you need to put the rule to match it. Now imagine an intern takes over the routing… this whole order-based routing would be an epic mess. > I was hoping there would be an alternative, but I guess regular expressions > are indeed the only option to do things properly. > > Did you have a particular API in mind? The parameter-based system is designed > to be much simpler while cover the most common use cases, but if you want > something highly customized, there will inevitably be some complexity to the > rules you set up. I was thinking about something like $args or $vars that would be pre-coded with the right regex to match one or no args and/or a query string. > Le 25 févr. 2015 à 20:57, Anthony <[email protected]> a écrit : > > On Wednesday, February 25, 2015 at 7:54:36 AM UTC-5, Louis Amon wrote: >> Anyway, the rules are processed in order, so you should be able to include a >> rule mapping static to static, and then include the /s$anything rule (which >> won't be matched to "static" because the static rule will already have >> matched). > > > That’s actually what I ended up doing, but it isn’t something you can rely on > in a big project… > > Why not? > >> In some cases, $anything isn't powerful enough, and you need to use regular >> expressions. > > I was hoping there would be an alternative, but I guess regular expressions > are indeed the only option to do things properly. > > Did you have a particular API in mind? The parameter-based system is designed > to be much simpler while cover the most common use cases, but if you want > something highly customized, there will inevitably be some complexity to the > rules you set up. > > Anthony > > -- > Resources: > - http://web2py.com <http://web2py.com/> > - http://web2py.com/book <http://web2py.com/book> (Documentation) > - http://github.com/web2py/web2py <http://github.com/web2py/web2py> (Source > code) > - https://code.google.com/p/web2py/issues/list > <https://code.google.com/p/web2py/issues/list> (Report Issues) > --- > You received this message because you are subscribed to a topic in the Google > Groups "web2py-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/web2py/sMPkRPjZWrg/unsubscribe > <https://groups.google.com/d/topic/web2py/sMPkRPjZWrg/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
