RouteMatcher named path parameters with regex

[Ranie Jade Ramiso]

Basically what I want is something like this:

 routeMatcher.get("/post/:id{[1-9][0-9]+}", ...)

It is exactly the same as named path parameters but a bit more restrictive. Matching only the id parameter if the regex inside the curly braces matches.

What is your opinion about this? I have started working on this in my local repo to support this.

Your input is much appreciated. :)

[Tim Fox]

Can't you already do this with regex matches?

http://vertx.io/core_manual_java.html#extracting-params-using-regular-expressions

On 27/06/13 04:11, Ranie Jade Ramiso wrote:

Basically what I want is something like this:

 routeMatcher.get("/post/:id{[1-9][0-9]+}", ...)

It is exactly the same as named path parameters but a bit more restrictive. 
Matching only the id parameter if the regex inside the curly braces matches.

What is your opinion about this?* *I have started working on this in my 
local repo to support this.

Your input is much appreciated. :)

[Ranie Jade Ramiso]

Yeah, but the captured groups are bounded to generic parameters names (e.g. paramn). Basically it just makes writing the route url much cleaner and easier to read :).

________________________________________________________________

Ranie Jade Ramiso <raniejaderamiso.com>

Software Engineer | Opensource Enthusiast | Professional Slacker 

Twitter | Facebook | Github

___________________________________________________________________________

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Tim Fox]

Right, I think this is because Java regex doesn't support named
capturing groups.

On 27/06/13 08:04, Ranie Jade Ramiso wrote:
> Yeah, but the captured groups are bounded to generic parameters names (e.g.

> param*n*). Basically it just makes writing the route url much cleaner and
> easier to read :).
>
> *________________________________________________________________*
> *
> *
> *Ranie Jade Ramiso <raniejaderamiso.com>*
> *Software Engineer | Opensource Enthusiast | Professional Slacker *
> *Twitter <https://twitter.com/raniejade> |
> Facebook<http://www.facebook.com/72878331c221485527705ba87e511306>|
> Github <https://github.com/raniejade>*
> *___________________________________________________________________________
> *

[Tim Fox]

Ah, no. Named capture group support was added in Java 7 it appears.

[Ranie Jade Ramiso]

Yes, named captured groups are supported. The current route matcher however always binds the parameters to the generic ones.

________________________________________________________________

Ranie Jade Ramiso <raniejaderamiso.com>

Software Engineer | Opensource Enthusiast | Professional Slacker 

Twitter | Facebook | Github

___________________________________________________________________________

email to vertx+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "vert.x" group.

To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.

[Yangming Huang]

Hi, Tim, is there any updates on this?

[Jose Antonio Illescas del Olmo]

Hi Tim, I'm new in vert.x community...

    This is an incredible feature, also you can add support for "." and "-" characters on placeholder names

I intend this...

  I have next URLs for address resource on my system:

     /addresses?customer.id={id}&accounts.id={id}

     /customers/{id}/addresses    =>    similar to    /addresses?customer.id={id}

     /accounts/{id}/addresses    =>    similar to    /addresses?accounts.id={id}

And y want only one handler to dispatch all request over "address" resource/subresource

   router.route("/customers/:customer.id/addresses").handler(ctx -> {

     ... (same handler than /addresses)

   });

   

   router.route("/account/:account.id/addresses").handler(ctx -> {

     ...  (same handler than /addresses)

   });

   

   router.route("/addresses").handler(ctx -> {

    ctx.response().putHeader("content-type", "text/html").end("/addresses?customer.id="+

                           ((ctx.request().getParam("customer.id")==null)?"":"?customer.id="+ctx.request().getParam("customer.id"))+

                           ((ctx.request().getParam("account.id")==null)?"":"&account.id="+ctx.request().getParam("account.id"));

   });

You can see that all URLs can processed by same unique handler...  (but currently only works for last route /address because placehoder name not allows "." and regexp capturing named-groups not works...)

I expect that you can appreciate this feedback to do vert.x "the best" asyncronous server of class

Thank You