aboutsummaryrefslogtreecommitdiffstats
path: root/actionpack/lib
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | | Only concatenate path if it was given rather than converting blindlyCarlos Antonio da Silva2014-07-311-1/+1
| | | | | |
* | | | | | Rename variable to better show its intentCarlos Antonio da Silva2014-07-311-12/+12
| | | | | |
* | | | | | Simplify conditionalCarlos Antonio da Silva2014-07-311-3/+2
| | | | | |
* | | | | | Push options check up so we can simplify internal methodsCarlos Antonio da Silva2014-07-311-13/+10
| | | | | |
* | | | | | Simplify code branch, remove #tapCarlos Antonio da Silva2014-07-311-7/+6
| | | | | |
* | | | | | Avoid a new hash objectCarlos Antonio da Silva2014-07-311-1/+1
| | | | | |
* | | | | | remove useless deupAaron Patterson2014-07-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | every call to default_resources_path_names allocates a new hash, no need to dup
* | | | | | push options inside the scope objectAaron Patterson2014-07-301-4/+9
| | | | | |
* | | | | | turn scope in to a linked listAaron Patterson2014-07-301-15/+36
| | | | | | | | | | | | | | | | | | | | | | | | this makes scope rollback much easier
* | | | | | remove alias_method_chainAaron Patterson2014-07-301-4/+2
| | | | | | | | | | | | | | | | | | | | | | | | we can `super` in to the previous implementation.
* | | | | | avoid instrospection on the moduleAaron Patterson2014-07-301-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | we already know what helpers are path helpers, so just iterate through that list and define the helpers with warnings
* | | | | | fix variable nameAaron Patterson2014-07-301-3/+3
| | | | | |
* | | | | | split path_helpers and url_helpersAaron Patterson2014-07-301-18/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | this lets us avoid hard coding a regexp for separating path and url helpers in the clear! method.
* | | | | | `add` will remove the method if it exists alreadyAaron Patterson2014-07-301-1/+0
| | | | | |
* | | | | | Deprecate `*_path` methods in mailers@schneems and @sgrif2014-07-303-51/+83
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Email does not support relative links since there is no implicit host. Therefore all links inside of emails must be fully qualified URLs. All path helpers are now deprecated. When removed, the error will give early indication to developers to use `*_url` methods instead. Currently if a developer uses a `*_path` helper, their tests and `mail_view` will not catch the mistake. The only way to see the error is by sending emails in production. Preventing sending out emails with non-working path's is the desired end goal of this PR. Currently path helpers are mixed-in to controllers (the ActionMailer::Base acts as a controller). All `*_url` and `*_path` helpers are made available through the same module. This PR separates this behavior into two modules so we can extend the `*_path` methods to add a Deprecation to them. Once deprecated we can use this same area to raise a NoMethodError and add an informative message directing the developer to use `*_url` instead. The module with warnings is only mixed in when a controller returns false from the newly added `supports_relative_path?`. Paired @sgrif & @schneems
* | | | | | Revert "Merge pull request #15305 from tgxworld/remove_unnecessary_require"Santiago Pastorino2014-07-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit f632f79b8dcd144408c66a544984b2ba9cf52f87, reversing changes made to 98c7fe87690ca4de6c46e8f69806e82e3f8af42d. Closes #16343
* | | | | | oops! :bomb:Aaron Patterson2014-07-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | use helpers.include? so we don't get any false positives
* | | | | | ask the named routes collection if the route is definedAaron Patterson2014-07-292-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | we should not be accessing internals to figure out if a method is defined.
* | | | | | helpers should be a Set so it doesn't grow unboundedAaron Patterson2014-07-291-4/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | since helpers is a set, we can be confident about when to remove methods from the module.
* | | | | | pass the module to define_named_route_methodsAaron Patterson2014-07-291-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | after this, we can disconnect @module from the instance
* | | | | | only ask for the routes module onceAaron Patterson2014-07-291-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | we can cache the module on the stack, then reuse it
* | | | | | eval_block should be privateAaron Patterson2014-07-291-0/+1
| | | | | |
* | | | | | remove the mounted? methodAaron Patterson2014-07-282-6/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | we know the routes should not be "optimized" when mounting an application
* | | | | | remove some cachingAaron Patterson2014-07-281-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | this caching doesn't increase performance, but does increase complexity. remove it for now and find better ways to speed up this code.
* | | | | | Fix protect_from_forgery docsDavid Albert2014-07-271-1/+1
| | | | | |
* | | | | | docs, add ref where to find valid `head` status symbols.Yves Senn2014-07-251-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | [ci skip]
* | | | | | Bug fix for assert_template when opening a new session.Guo Xiang Tan2014-07-251-5/+9
| | | | | | | | | | | | | | | | | | | | | | | | See https://github.com/rails/rails/pull/16234#commitcomment-7115670.
* | | | | | Fix AC::TemplateAssertions instance variables not resetting.Guo Xiang Tan2014-07-212-5/+8
| | | | | | | | | | | | | | | | | | | | | | | | Fixes https://github.com/rails/rails/issues/16119.
* | | | | | LOCALHOST definition should match any 127.0.0.0/8 addressEarl J St Sauver2014-07-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The entire 127.0.0.0/8 range is assigned to the loopback address, not only 127.0.0.0/24. This patch allows ActionDispatch::Request::LOCALHOST to match any IPv4 127.0.0.0/8 loopback address. The only place that the #local? method was previously under test was in the show_expectations_test.rb file. I don't particularly like that that's implicitly where this code is under test, and I feel like I should move some of that testing code into the test/dispatch/request_test.rb file, but I wanted some feedback first. Credit goes to @sriedel for discovering the issue and adding the patch.
* | | | | | Prefer to pass block when logging.Guo Xiang Tan2014-07-181-25/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Logger by default includes a guard which checks for the logging level. By removing the custom logging guards, we can decouple the logging guard from the logging action to be done. This also follows the good practice listed on http://guides.rubyonrails.org/debugging_rails_applications.html#impact-of-logs-on-performance.
* | | | | | `recall` should be `path_parameters`, also make it requiredAaron Patterson2014-07-171-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "recall" is a terrible name. This variable contains the parameters that we got from the path (e.g. for "/posts/1" it has :controller => "posts", :id => "1"). Since it contains the parameters we got from the path, "path_parameters" is a better name. We always pass path_parameters to `generate`, so lets make it required.
* | | | | | pass the route name to define_url_helperAaron Patterson2014-07-172-22/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | this allows us to avoid 2 hash allocations per named helper definition, also we can avoid a `merge` and `delete`.
* | | | | | use a strategy object for generating urls in named helpersAaron Patterson2014-07-172-21/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | since we know that the route should be a path or fully qualified, we can pass a strategy object that handles generation. This allows us to eliminate an "if only_path" branch when generating urls.
* | | | | | extract path building to a methodAaron Patterson2014-07-161-9/+11
| | | | | |
* | | | | | break out path building logic to methodsAaron Patterson2014-07-161-14/+22
| | | | | |
* | | | | | only extract :params from the options hash onceAaron Patterson2014-07-161-3/+2
| | | | | |
* | | | | | we do not need to dup the options hash, it is private and a new object each callAaron Patterson2014-07-161-2/+2
| | | | | |
* | | | | | push rails app testing upAaron Patterson2014-07-161-9/+13
| | | | | | | | | | | | | | | | | | | | | | | | this way we only have to test for whether it is a rails app once.
* | | | | | Rails-ish apps should descend from Rails::RailtieAaron Patterson2014-07-161-8/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use an is_a check to ensure it's a Railsish app so we can avoid respond_to calls everywhere.
* | | | | | app should always be a class (I suppose)Aaron Patterson2014-07-161-1/+1
| | | | | |
* | | | | | we should be checking if the app is a classAaron Patterson2014-07-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hopefully `object.class` always returns something that is_a?(Class), so the previous logic didn't really make sense.
* | | | | | extract inner options before delegating to the helperAaron Patterson2014-07-161-7/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If we extract the options from the user facing method call ASAP, then we can simplify internal logic.
* | | | | | always transcode the file to utf-8Aaron Patterson2014-07-161-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | people may be passing filenames to the constructor that are not utf-8, but they will assome that calling `original_filename` returns utf-8 (because that's what it used to do).
* | | | | | Don't accept parameters as argument for redirect to [via @homakov]Santiago Pastorino2014-07-161-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Closes #16170
* | | | | | routed applications will respond to these methodsAaron Patterson2014-07-152-2/+2
| | | | | |
* | | | | | rack 1.6 encodes the filenames in posts correctly nowAaron Patterson2014-07-151-8/+1
| | | | | |
* | | | | | RouteSet should be in charge of constructing the dispatherAaron Patterson2014-07-152-8/+13
| | | | | | | | | | | | | | | | | | | | | | | | Now we can override how requests are dispatched in the routeset object
* | | | | | Stash original path in `ShowExceptions` middlewareGrey Baker2014-07-141-0/+1
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `ActionDispatch::ShowExceptions` overwrites `PATH_INFO` with the status code for the exception defined in `ExceptionWrapper`, so the path the user was visiting when an exception occurred was not previously available to any custom exceptions_app. The original `PATH_INFO` is now stashed in `env["action_dispatch.original_path"]`.
* | | | | Use `#bytesize` instead of `#size` when checking for cookie overflowAgis-2014-07-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Although the cookie values happens to be ASCII strings because they are Base64 encoded, it is semantically incorrect to check for the number of the characters in the cookie, when we actually want to check for the number of the bytes it consists of. Furthermore it is unecessary coupling with the current implementation that uses Base64 for encoding the values.
* | | | | Removed single space padding from empty response body.Godfrey Chan2014-07-101-6/+2
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `render nothing: true` or rendering a `nil` body no longer add a single space to the response body. The old behavior was added as a workaround for a bug in an early version of Safari, where the HTTP headers are not returned correctly if the response body has a 0-length. This is been fixed since and the workaround is no longer necessary. Use `render body: ' '` if the old behavior is desired.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 10:03:34 +0000