- 26 8月, 2015 3 次提交
-
-
由 Aaron Patterson 提交于
collect the body and make assert against the collected body
-
由 Aaron Patterson 提交于
This saves a lambda and request allocation on each request.
-
由 amitkumarsuroliya 提交于
-
- 25 8月, 2015 8 次提交
-
-
由 Marcin Olichwirowicz 提交于
-
由 Anshul Sharma 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
We should keep the route set generation logic in one place
-
由 Aaron Patterson 提交于
If we subclass and augment the superclass, then we don't need to have setters for particular things on the superclass.
-
由 Gaurav Sharma 提交于
`
💅 ` -
由 Aaron Patterson 提交于
controller class resolution has been moved to the request object, so we should override that method instead of relying on the RouteSet to generate the controller class.
-
- 24 8月, 2015 3 次提交
-
-
由 Marcin Olichwirowicz 提交于
-
由 akihiro17 提交于
-
由 Aditya Kapoor 提交于
-
- 23 8月, 2015 1 次提交
-
-
由 Aaron Patterson 提交于
This commit allows us to use one request object rather than allocating multiple request objects to deal with the session.
-
- 22 8月, 2015 3 次提交
-
-
由 eileencodes 提交于
This refactoring moves the controller class name that was on the route set to the request. The purpose of this refactoring is for changes we need to move controller tests to integration tests, mainly being able to access the controller on the request instead of having to go through the router. [Eileen M. Uchitelle & Aaron Patterson]
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
I'm going to change the constructor, so it's easier to do it in one place.
-
- 21 8月, 2015 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 19 8月, 2015 2 次提交
-
-
由 Aaron Patterson 提交于
nobody should be touching the routes hash without going through the NamedRouteCollection object.
-
由 Aaron Patterson 提交于
-
- 18 8月, 2015 4 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
I want to change the real constructor to take a particular parameter for matching the request method
-
由 Aaron Patterson 提交于
The string we create is almost always the same, so rather than joining all the time, lets join once, then reuse that string everywhere.
-
- 16 8月, 2015 1 次提交
-
-
由 Aaron Patterson 提交于
We should build the routes using the user facing API which is `Mapper`. This frees up the library internals to change as we see fit. IOW we shouldn't be testing internals.
-
- 15 8月, 2015 12 次提交
-
-
由 Aaron Patterson 提交于
The outer router object already keeps a hash of named routes, so we should just use that.
-
由 Aaron Patterson 提交于
refactor the tests with a backwards compatible method call so we can rm add_route2 from the journey router
-
由 Aaron Patterson 提交于
then we can let the mapping object derive stuff that the Route object needs.
-
由 Aaron Patterson 提交于
now that we aren't doing options manipulations, we can just pass the mapping object down and read values from it.
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
now we don't need to add it to a hash and delete it from the hash later just to pass it around
-
由 Aaron Patterson 提交于
`add_route` needs the AST, so rather than shove it in a hash and delete later, lets move parsing up the stack so we can pass down later
-
由 Aaron Patterson 提交于
also change the feeler to subclass AD::Request so that it has all the methods that Request has
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
Eventually I want to eliminate the FakeSet test class
-
由 Aaron Patterson 提交于
I'm going to reimplement this using route objects, so it will be easier if we just change ast access to go through a method rather than hashes
-
由 Aaron Patterson 提交于
we don't need to keep adding it and deleting if from hashes.
-
- 14 8月, 2015 2 次提交
-
-
由 Aaron Patterson 提交于
This was a useless object. We can just directly construct a Path::Pattern object without a Strexp object.
-
由 Aaron Patterson 提交于
the caller already has it, there is no reason to pack it in to an object and just throw that object away.
-