Sawyer X

http://blogs.perl.org/users/sawyer_x/ [email protected]

@bookingcom Amsterdam, the Netherlands

Results 167 comments of


Sawyer X

make uri_for receive a name for a route

We're pushing hard to finish the plugins work for this release (hopefully going out on Sunday, tomorrow). I can try and prepare a sample to test out today and tomorrow....

make uri_for receive a name for a route

@mickeyn suggested adding a set of keywords to be **named**, such as `named_get`, `named_post`, `named_del`, etc. How does that sound to people? ``` # in code named_get display_product => '/view/product/:id'...

make uri_for receive a name for a route

Let's bump this back up! :)

make uri_for receive a name for a route

I've given this a bit more thought. I think we don't need new DSL keywords. There are only two ways to call `get`: `get '/' => sub {...}` `get '/'...

make uri_for receive a name for a route

I wrote the sample code. I'll put up a PR for discussion.

make uri_for receive a name for a route

PR pushed: #1270. :)

make uri_for receive a name for a route

I updated the PR with a new keyword: `uri_for_route`, but it's still not perfect.

Add "typical" mistakes to documentation

Where do you suggest putting this?

Allow send_error to send different content types

You would need to refactor the logic in `send_as` so it isn't repeated.

Sub pathname_exists makes debugging hard with the return eval {...} approach

Can you submit this as a pull request?