aboutsummaryrefslogtreecommitdiffstats
path: root/actionpack/test
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | | | use a custom request class to determine the controller classAaron Patterson2015-08-241-23/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | | | Merge pull request #21355 from akihiro17/remove-variablesRafael Mendonça França2015-08-241-2/+2
|\ \ \ \ \ \ \ | |_|_|/ / / / |/| | | | | | Remove unused variables
| * | | | | | Remove unused variablesakihiro172015-08-241-2/+2
| | |/ / / / | |/| | | |
* | | | | | Merge pull request #21321 from rodzyn/removing_mochaKasper Timm Hansen2015-08-2410-78/+103
|\ \ \ \ \ \ | |/ / / / / |/| | | | | Get rid of mocha tests in actionpack - part 1
| * | | | | Get rid of mocha tests - part 1Marcin Olichwirowicz2015-08-2410-78/+103
| | | | | |
* | | | | | use a request object in the session middlewareAaron Patterson2015-08-222-22/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit allows us to use one request object rather than allocating multiple request objects to deal with the session.
* | | | | | Refactor to remove controller class from route to requesteileencodes2015-08-221-1/+1
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]
* | | | | pass a request object to the headers objectAaron Patterson2015-08-211-1/+1
| | | | |
* | | | | move header allocation to a helper methodAaron Patterson2015-08-211-5/+9
| | | | | | | | | | | | | | | | | | | | | | | | | I'm going to change the constructor, so it's easier to do it in one place.
* | | | | Merge pull request #21106 from amitsuroliya/fix_routing_testAndrew White2015-08-211-6/+0
|\ \ \ \ \ | |_|_|_|/ |/| | | | Remove duplicity in tests
| * | | | Remove duplicity in testsamitkumarsuroliya2015-08-031-6/+0
| |/ / /
* | | | point at rack masterAaron Patterson2015-08-201-1/+1
| | | |
* | | | make the routes reader privateAaron Patterson2015-08-181-1/+1
| | | | | | | | | | | | | | | | | | | | nobody should be touching the routes hash without going through the NamedRouteCollection object.
* | | | symbols will always be constructed with strings. :bomb:Aaron Patterson2015-08-181-1/+1
| | | |
* | | | test the verb method on the route, specificallyAaron Patterson2015-08-171-1/+1
| | | |
* | | | routes are always constructed with a hash for the conditionsAaron Patterson2015-08-173-4/+4
| | | |
* | | | introduce an alternate constructor for Route objectsAaron Patterson2015-08-171-12/+12
| | | | | | | | | | | | | | | | | | | | I want to change the real constructor to take a particular parameter for matching the request method
* | | | default pattern to use a joined stringAaron Patterson2015-08-172-13/+15
| | | | | | | | | | | | | | | | | | | | The string we create is almost always the same, so rather than joining all the time, lets join once, then reuse that string everywhere.
* | | | use the mapper to build the routing tableAaron Patterson2015-08-152-231/+103
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | only keep one hash of named routesAaron Patterson2015-08-142-13/+14
| | | | | | | | | | | | | | | | | | | | The outer router object already keeps a hash of named routes, so we should just use that.
* | | | rm add_route2Aaron Patterson2015-08-142-41/+51
| | | | | | | | | | | | | | | | | | | | refactor the tests with a backwards compatible method call so we can rm add_route2 from the journey router
* | | | pass pass the mapping object down the add_route stackAaron Patterson2015-08-141-1/+1
| | | | | | | | | | | | | | | | | | | | then we can let the mapping object derive stuff that the Route object needs.
* | | | pass the mapping object to build_routeAaron Patterson2015-08-141-16/+5
| | | | | | | | | | | | | | | | | | | | now that we aren't doing options manipulations, we can just pass the mapping object down and read values from it.
* | | | deprecate passing a string for both the beginning path and :path optionAaron Patterson2015-08-141-1/+4
| | | |
* | | | pass the path ast downAaron Patterson2015-08-141-1/+1
| | | | | | | | | | | | | | | | | | | | now we don't need to add it to a hash and delete it from the hash later just to pass it around
* | | | pull up path parsingAaron Patterson2015-08-141-1/+2
| | | | | | | | | | | | | | | | | | | | `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
* | | | use predicate methods instead of hard coding verb stringsAaron Patterson2015-08-142-6/+6
| | | | | | | | | | | | | | | | | | | | also change the feeler to subclass AD::Request so that it has all the methods that Request has
* | | | implement `requirements` in terms of routesAaron Patterson2015-08-141-1/+1
| | | |
* | | | implement the `asts` method in terms of paths / patternsAaron Patterson2015-08-141-12/+11
| | | | | | | | | | | | | | | | Eventually I want to eliminate the FakeSet test class
* | | | extract ast finding to a methodAaron Patterson2015-08-141-9/+13
| | | | | | | | | | | | | | | | | | | | 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
* | | | stop adding path_info to the conditions hashAaron Patterson2015-08-141-9/+9
| | | | | | | | | | | | | | | | we don't need to keep adding it and deleting if from hashes.
* | | | remove StrexpAaron Patterson2015-08-134-74/+61
| | | | | | | | | | | | | | | | | | | | This was a useless object. We can just directly construct a Path::Pattern object without a Strexp object.
* | | | pass anchor directly to `Pattern`Aaron Patterson2015-08-134-39/+38
| | | | | | | | | | | | | | | | | | | | the caller already has it, there is no reason to pack it in to an object and just throw that object away.
* | | | pull up options_constrants extractionAaron Patterson2015-08-131-1/+1
| | | |
* | | | remove `as`Aaron Patterson2015-08-131-1/+1
| | | | | | | | | | | | | | | | the caller already has access to `as`, so we can stop passing it around.
* | | | remove anchor from mappingAaron Patterson2015-08-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | the same value that is extracted from the options hash earlier is returned, so we don't need to pass it in in the first place. The caller already has the data, so stop passing it around.
* | | | pull `anchor` extraction upAaron Patterson2015-08-131-1/+1
| | | | | | | | | | | | | | | | | | | | this way we don't have to mutate the options hash so far away from where the user passed it in
* | | | raise if `anchor` is passed to `scope`Aaron Patterson2015-08-131-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | The `anchor` parameter [is overridden](https://github.com/rails/rails/blob/b4b4a611d0eb9aa1c640c5f521c6a43bf2a65bab/actionpack/lib/action_dispatch/routing/mapper.rb#L1528) unless it is directly passed to `match`, so setting it in a scope must be a mistake.
* | | | pull `formatted` up the stackAaron Patterson2015-08-121-1/+10
| | | | | | | | | | | | | | | | this reduces the number of times we have to mutate the options hash.
* | | | add a regression test for scoped `format` paramsAaron Patterson2015-08-121-0/+11
| | | | | | | | | | | | | | | | This just ensures that `format` is applied to things inside the scope
* | | | add a regression test for adding arbitrary keys to `scope`Aaron Patterson2015-08-121-0/+15
| | | |
* | | | add a method to `Scope` for getting mapping optionsAaron Patterson2015-08-121-1/+2
| | | | | | | | | | | | | | | | | | | | Eventually we don't want to expose the "options" hash from scope, only read values from it. Lets start by adding a reader method.
* | | | pull `via` all the way out of `add_route`Aaron Patterson2015-08-121-0/+8
| | | |
* | | | add a test for adding "via" using `scope`Aaron Patterson2015-08-121-0/+9
| | | |
* | | | pull `via` extraction upAaron Patterson2015-08-121-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | We're going to try pulling this up further, and check `via` validity sooner. This way we don't have to do a bunch of processing on `options` hashes only to find out that the route is incorrect
* | | | Merge pull request #21203 from denniss/issue-21199Sean Griffin2015-08-111-0/+8
|\ \ \ \ | | | | | | | | | | Authorization scheme should be case insensitive. Fixes #21199
| * | | | Authorization scheme should be case insensitive. Fixes #21199Dennis Suratna2015-08-111-0/+8
| | | | |
* | | | | pull `to` upAaron Patterson2015-08-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | this way we don't have to insert / delete it from the options hash so many times.
* | | | | push option decomposition up a bit moreAaron Patterson2015-08-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | I think we can find the original place where `action` is added to the options hash now.
* | | | | pull up the "options.delete(:controller)" logicAaron Patterson2015-08-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | we want to try to pull this logic up to where the user actually passed in "controller" so that it's close to the related call. That way when we're down the stack, we don't need to wonder "why are we doing this?"