| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
[ci skip]
|
|
|
|
|
| |
http links will be redirected to the https version, but still better to
just directly link to the https version.
|
|
|
|
|
| |
In this context, the phrase 'product instance' refers to the Product class,
so capitalize it.
|
|
|
|
|
|
|
| |
[ci skip] A regular expression was used to find a lot of missing Oxford
commas and add them. The regular expression was as follows.
", ([a-zA-Z0-9.\`:'\"]+ ){1,6}(or|and) "
|
|
|
|
|
|
|
|
|
| |
- Remove mention about `ActionView::TemplateHandlers` since this
module was removed by c1304098cca8a9247a9ad1461a1a343354650843.
Change word `subclasses` to `nested classes`.
See c7408a0e40545558872efb4129fe4bf097c9ce2f
- Remove useless sentence "Beginning with Rails 2, the standard extensions
are `.erb` for ERB (HTML with embedded Ruby), and `.builder` for Builder (XML generator)."
|
|
|
|
| |
from text/html to text/plain. (#31212)
|
| |
|
|
|
|
|
|
|
| |
While the code example was not unsafe, it
encourages the use of confusingly unsafe APIs
(specifically `html_safe`). We have a safe
alternative and we should encourage people to use
it under all circumstances.
|
|
|
|
|
|
|
|
|
| |
* The example code on this page are similar to ones generated
by scaffold generator, but some points are different.
* Of course, it is no reason to be as same as scaffolding codes.
But this is the guide for beginners, I thought it's better
to be almost same as scaffolding codes.
|
|
|
|
|
| |
Ref: https://github.com/rack/rack/commit/5401f776f660b1f8d0e0650ba78478d7488eff75,
https://github.com/rack/rack/commit/73e08279d4433ca66cf22157a40dba562629031a
|
|
|
| |
When using render plain the extension for the layout needs to be .text.erb instead of .txt.erb
|
|
|
|
|
| |
Clarify the partial local variable name as being the same as the name
of the partial, minus the _leading_ underscore.
|
|
|
|
|
| |
This allows auto_discovery_link_tag to support the JSON Feed standard.
See https://jsonfeed.org/version/1 for more information.
|
|
|
|
| |
Switch extension 👉 format as it's more apt here.
|
| |
|
|
|
|
|
|
|
| |
The guide contains a typo in the "local_assigns" section, where
rendering a model named 'Article' via `render @articles` is shown to
render a partial called `_articles.html.erb`, when in fact the necessary
partial name is `_article.html.erb`
|
|
|
| |
Changed "same way they do" to "same way they are".
|
|
|
| |
Update render yield docs to use `search` local variable instead of `@q` instance variable
|
|\ |
|
| | |
|
| |
| |
| |
| | |
behavior in 2.3.2, but dont specify that is not halting. Its better to not let developers be caught by surprise. [ci skip]
|
|/ |
|
|
|
|
|
|
|
|
| |
In the latest security releases render with a trailing slash no more call
render :file.
Also add a note about the security implications of using it with user
parameters.
|
| |
|
| |
|
|
|
|
| |
`:nothing` option was deprecated in 44781b6e9790d90b4f8b9a41d2b2c114b1a582ee
|
|
|
|
|
|
|
| |
if not marked as safe by using html_safe
Fixes #22648
[ci skip]
|
| |
|
|
|
|
|
|
|
| |
Applications that use `redirect_to :back` can be forced to 500 by
clients that do not send the HTTP `Referer` (sic) header.
`redirect_back` requires the user to consider this possibility up front
and avoids this trivially-caused application error.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`redirect_to :back` is a somewhat common pattern in Rails apps, but it
is not completely safe. There are a number of circumstances where HTTP
referrer information is not available on the request. This happens often
with bot traffic and occasionally to user traffic depending on browser
security settings.
When there is no referrer available on the request, `redirect_to :back`
will raise `ActionController::RedirectBackError`, usually resulting in
an application error.
`redirect_back` takes a required `fallback_location` keyword argument
that specifies the redirect when the referrer information is not
available. This prevents 500 errors caused by
`ActionController::RedirectBackError`.
|
| |
|
| |
|
|
|
|
| |
rack/rack#754
|
|
|
|
| |
`head` method works similar to `render` method with `:nothing` option
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a squash of the following commits, from first to last:
-
Fix minor, random things I’ve come across lately that individually
did not seem worth making a PR for, so I saved them for one commit.
One common error is using “it’s” (which is an abbreviation of “it is”)
when the possessive “its” should be used for indicating possession.
-
Changes include the name of a test, so remove the `[skip ci]` (thanks @senny).
-
Line wrap the changes at 80 chars and add one more doc fix.
-
Add a missing line wrap in the Contributing to Ruby on Rails Guide.
-
Line wrap the `TIP` section in the Contributing to Ruby on Rails Guide as well.
Rendering the guide locally with `bundle exec rake guides:generate` did
not show any change in on-screen formatting after adding the line wrap.
The HTML generated is (extra line added to illustrate where the line
wrap takes place):
<div class="info"><p>Please squash your commits into a single commit
when appropriate. This
simplifies future cherry picks and also keeps the git log
clean.</p></div>
-
Squash commits.
|
| |
|
|
|
|
|
|
| |
* Fix a few typos
* Wrap some lines around 80 chars
* Rephrase some statements
|
| |
|
| |
|
|\
| |
| | |
Guides: Template Inheritance (new in guides, feature in since 3.1)
|
| |\ |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
Add docs about local_assigns on guides
|
| | | |
| | | |
| | | |
| | | | |
[ci skip]
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Changed `IN` to `ON` in markdown renderer condition
|
| | | | |
| | | | |
| | | | |
| | | | | |
- Changed `IN` to `ON` in all note sentences in guides.
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Make possible to use blocks with short version of render partial
Conflicts:
actionview/CHANGELOG.md
|