Return route objects when defining new ones#1088
Closed
Conversation
Member
|
We don't specify the return values of most keywords, however returning the route object(s) makes sense here. @xsawyerx++ We should document and add tests before merging though. ;) |
Member
|
Sounds like a good and useful idea - @xsawyerx ++ |
Member
Author
|
I'll add some tests and docs. As the ticket now reflects, I want this for what I'm playing with in #33. :) |
This commit adds the ability to receive all the route objects created with the call to the DSL that creates them. This is helpful if you want to know which objects you just created. An example could be a plugin that creates a route (or receives a route created) and wants to inspect it or alter it. Future thoughts: * What if we had hooks for route creation? * What if routes had unique IDs?
xsawyerx
force-pushed
the
feature/tracking-route-specs
branch
from
7943a73 to
2269bd3
Compare
Member
Author
|
@racke Added a test showcasing it. I prefer not to add documentation for it because:
Can I merge it now? :) |
Member
|
Good, go ahead! |
Member
|
👍 |
Member
xsawyerx
added a commit
that referenced
this pull request
Jan 12, 2016
[ BUG FIXES ]
* GH #1013, #1092: Remove race condition caused by caching available
engines. (Sawyer X, Menno Blom, Russell Jenkins)
* GH #1089: Exact macthing of route regex comments for tokens/splats.
(Sawyer X)
* GH #1079, #1082: Allow routes to return '0' as response content,
and serializer hooks are called when default response content is
to be returned. (Alberto Simões, Russell Jenkins)
* GH #1093, 1095: Use a dynamic TT2 INCLUDE_PATH to allow relative
views with relative includes; fixing regression introduced by #1037.
(Russell Jenkins)
* GH #1096, #1097: Return compatibility on Perl 5.8.x!
(Peter Mottram - @SysPete)
[ DOCUMENTATION ]
* GH #1076: Typo in Dancer2::Core::Hook POD. (Jonathan Scott Duff)
[ ENHANCEMENTS ]
* GH #1074: Add sample session engine config to skeleton app.
(Peter Mottram - @SysPete)
* GH #1088: Return route objects when defining new routes.
(Sawyer X)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit adds the ability to receive all the route objects
created with the call to the DSL that creates them.
This is helpful if you want to know which objects you just
created. An example could be a plugin that creates a route (or
receives a route created) and wants to inspect it or alter it.
Future thoughts: