| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Removes most mentions of secrets.secret_key_base and explains
credentials instead.
Also removes some very stale upgrade notices about Rails 3/4.
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`rack-mount` switched to journey with 5f0b37c.
Also, `rack-cache` will not be used unless you explicitly specify it.
Ref:
https://github.com/rails/rails/commit/037e50ec39c7c3d58a102a6584e2740652420d1d
https://github.com/rails/rails/commit/1fc795468525d8622cdca474a54c8310a514aa46
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Don't use remove_method or remove_possible_method just before a new
definition: at best the purpose is unclear, and at worst it creates a
race condition.
Instead, prefer redefine_method when practical, and
silence_redefinition_of_method otherwise.
|
| |
| |
| |
| | |
[ci skip]
|
|\ \
| |/
|/| |
Add documentation about template partial caching
|
| |
| |
| |
| |
| |
| |
| | |
Motivation:
- #29423 surfaced some confusion about how template caching works when
using partials across files with different mime types. This doc
attempts to explain how this can be accomplished.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
skip]
This is a partial revert of 07402aa1307a4ff71b4ef6581f95b8612238a6af.
I also changed "cache-key" to "cache key" because "cache-key" appears
only once in the repo.
```
% git grep '\bcache-key\b' | wc -l
1
% git grep '\bcache key\b' | wc -l
28
```
|
|\ \
| | |
| | | |
Update Caching with Rails guide [ci skip]
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
Fix grammar in JavaScript in Rails [ci skip]
|
| | |
| | |
| | |
| | | |
* I've fixed grammar problems in the guide about JavaScript in Rails.
|
|/ / |
|
| |
| |
| | |
I had to do some I was unsure what kind of caching it was performing, and had to do some Googling. Also improves the wording.
|
|\ \
| | |
| | | |
Fix indentation [ci skip]
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
[ci skip]Revert commits changing wrong place
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commits 5147ab121d628f29451c654a8c312d5a3f491ffb and 391043ab04007bfd4c4c4c8e8d3308c1eae60175.
These commits looked to intend to change documents of has_many dependent options, but actually changed documents of belongs_to dependent options.
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Do not generate default alt text for images
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- Auto-generating content from the filename of an image is not suitable
alternative text; alt text that isn't fully considered can be
distracting and fatiguing for screen readers users (blind, low vision,
dyslexic people).
- Setting a filename fallback short circuits screen reader default
behavior and configuration for blank descriptions.
- Setting poor defaults also creates false negatives for accessibility
linting and testing software, that makes it harder to improve
application accessibility.
***
- After this change, if authors leave images without alt text, screen
readers will fallback to default behavior for missing alt text.
- Also with this change, Automated linting and testing tools will
correctly generate warnings.
[Fixes #30096]
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Changed the phrase '... and many more high targets' to '... and many more high _profile_ targets'
|
| | | | | |
|
| |_|/ /
|/| | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
[ci skip] form_with in the getting started guide.
|
| |/ / /
| | | |
| | | |
| | | | |
Add back a bit about a resource oriented style of routing.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Add Contributing to the Rails Code link.
* Wiki link for Spanish is redirect.
* The base branch of Polish repo is master. And Turkish is, too.
* Unified expression `rails-dev-box`
* The Clone url is wrong.
* The mailing list url is old.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Update generator guide [ci skip]
|
| | | | | |
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | | |
[ci skip]
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
yhirano55/update_rails_initialization_process_guide
Update The Rails Initialization Process of guide [ci skip]
|
| | | | | |
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | | |
Follow up of 2ebb284ef5bf2c36bd8ba0a4524cab83810f12ab.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
* Update url in Development Dependencies Install
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Lots of grammar cleanup, and also changing to use macOS.
[ci skip]
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a requirement when working on the JS portions of ASt. Using
npm instead of Yarn is a bad idea here since the lockfile is in Yarn's
format.
[ci skip]
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The initial commit (efaa6e4f79d457c2cdd08cbc56d63bc972a6993c) that changed this
behavior was intended to be a minor change, but ended up becoming a
large-ish breaking change within Active Record.
This is because instead of only JSON encoding `Hash`es or `Array`s in `#serialize`,
we now encode all values passed in. This is an issue if you're passing in a `String`,
that has already been transformed from a `Hash` to a `String`, since your data
is now being double encoded.
Unfortunately, the change was included in one of the v5.0.0 beta
releases, and it is too late to revert without huge ripple effects.
Thus, all we can do is update the documentation (via this commit), and
add some test coverage (coming soon in a PR) for the new behavior.
Please note that in the documentation I talk about deserialization, not
about serialization, where the actual change occurred. This is because
you won't notice any changes in serialized data until you try and
deserialize it. Also to make the change itself (confusing until you
read through everything multiple times) easier to understand.
Related #27788, #25594, #26101, #24234, #28292, #28285, #28285, and
probably others.
[ci skip]
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
about passing string to `:if` and `:unless`.
This is a follow up to https://github.com/rails/rails/pull/28058 [ci
skip]
|
| | |
| | |
| | |
| | |
| | |
| | | |
Changed sentence to be more clear
[ci skip]
|