| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
These methods mutate the path variable/argument so there is no need
to reassign it every time.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
every call to default_resources_path_names allocates a new hash, no need
to dup
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
this makes scope rollback much easier
|
| | | |
| | | |
| | | |
| | | | |
we can `super` in to the previous implementation.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
we already know what helpers are path helpers, so just iterate through
that list and define the helpers with warnings
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
this lets us avoid hard coding a regexp for separating path and url
helpers in the clear! method.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit f632f79b8dcd144408c66a544984b2ba9cf52f87, reversing
changes made to 98c7fe87690ca4de6c46e8f69806e82e3f8af42d.
Closes #16343
|
| | | |
| | | |
| | | |
| | | | |
use helpers.include? so we don't get any false positives
|
| | | |
| | | |
| | | |
| | | |
| | | | |
we should not be accessing internals to figure out if a method is
defined.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
since helpers is a set, we can be confident about when to remove methods
from the module.
|
| | | |
| | | |
| | | |
| | | | |
after this, we can disconnect @module from the instance
|
| | | |
| | | |
| | | |
| | | | |
we can cache the module on the stack, then reuse it
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
we know the routes should not be "optimized" when mounting an
application
|
| | | |
| | | |
| | | |
| | | |
| | | | |
this caching doesn't increase performance, but does increase complexity.
remove it for now and find better ways to speed up this code.
|
| | | |
| | | |
| | | |
| | | | |
Fixes https://github.com/rails/rails/issues/16119.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
"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.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
this allows us to avoid 2 hash allocations per named helper definition,
also we can avoid a `merge` and `delete`.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
this way we only have to test for whether it is a rails app once.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Use an is_a check to ensure it's a Railsish app so we can avoid
respond_to calls everywhere.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Hopefully `object.class` always returns something that is_a?(Class), so
the previous logic didn't really make sense.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
If we extract the options from the user facing method call ASAP, then we
can simplify internal logic.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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).
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Now we can override how requests are dispatched in the routeset object
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
`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"]`.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Because URI paths may contain non US-ASCII characters we need to force
the encoding of any unescaped URIs to UTF-8 if they are US-ASCII.
This essentially replicates the functionality of the monkey patch to
URI.parser.unescape in active_support/core_ext/uri.rb.
Fixes #16104.
|
| | | |
|
|\ \ \
| | | |
| | | | |
This updates rails to use edge rack
|
| | | |
| | | |
| | | |
| | | | |
https://github.com/rack/rack/commit/5a5aee36
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As Rack has some non backwards compatible changes added required
modifications to keep behaviour in rails close to same as before.
Also modified generators to include rack/rack for not yet released
version of rack
|
| | | |
| | | |
| | | |
| | | | |
It always responds to mounted_helpers now
|