| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Use app namespace for framework tasks
|
| |
| |
| |
| | |
(e.g. `rails:update` and `rails:template` tasks is renamed to `app:update` and `app:template`.)
|
| | |
|
|\ \
| | |
| | |
| | | |
Create tmp folder if not present
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
All Apps may not have a tmp folder
Update dev.rake
Update dev.rake
Update dev.rake
Update dev.rake
Update dev.rake
Update dev.rake
Update dev.rake
|
|/ / |
|
|/
|
|
|
| |
Puma 3.0 and up introduced compatibility to read from `config/puma.rb` when booting from the command `$ rails server`https://github.com/puma/puma/pull/856.
|
|\
| |
| | |
Enable HSTS with IncludeSubdomains header by default for new apps
|
| | |
|
| |
| |
| |
| |
| | |
- We will remove the initializer for old apps which are migrated to
Rails 5 so that they are not affected by this breaking change.
|
| |
| |
| |
| |
| |
| | |
subdomains
- We will reuse config.ssl_options for setting the HSTS settings.
|
|\ \
| |/
|/|
| |
| | |
y-yagi/correctly_check_ApplicationRecord_in_mountable_engine
correctly check `ApplicationRecord` is exist in moutable engine
|
| |
| |
| |
| | |
Follow up to 1813b29fc7632959800252f36e4b2e6ed4ac7266
|
|\ \
| | |
| | | |
Fix README heading according to Markdown conventions
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The first heading in some README's are indicated using a second level
heading (`##`), which in my opinion is of incorrect structure.
Therefore, in this patch I changed the first heading to a first level
heading (`#`) in README's where this incorrect structure occurs.
[ci skip]
|
| | | |
|
| | |
| | |
| | |
| | | |
This also marks Action Cable routes as internal to Rails.
|
| | | |
|
| | |
| | |
| | |
| | | |
Adds changelog headers for beta3 release
|
| | |
| | |
| | |
| | | |
Fixes #23855
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
coffee-rails is stable now so we don't need to point to the master
branch.
|
|\ \ \
| |/ /
|/| | |
Show permitted flag in the output of AC::Parameters#inspect
|
| | |
| | |
| | |
| | | |
- Fixes #23822.
|
|\ \ \
| |/ /
|/| | |
AppGenerator: Replace 'rake' with 'rails_command'
|
| | |
| | |
| | |
| | |
| | | |
Follows the convention from Rails 5 of invoking tasks on the command-line
with `rails …` rather than `rake …`.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since Rails 5.0 is switching the Rails command line from 'rake …'
to 'rails …', it makes sense to also replace the `rake` method in
the Rails templates API.
Based on feedback from @matthewd and @kaspth, I chose to replace
`rake` with `rails_command`, which is less confusing than
the alternatives `rails` or `command` or `rails_run` and is not
Thor-reserved word like `task`.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a rebased version of #22825.
Closes #22825.
|
| | |/
| |/|
| | |
| | | |
environment templates
|
| | | |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
Alternative to #23638 log to STDOUT via env var
|
| | |
| | |
| | |
| | |
| | |
| | | |
People who deploy to containers or other places where they might have some sort of a log wrapping service use stdout. With this change new rails apps can be configured to output to STDOUT via setting `RAILS_LOG_TO_STDOUT` to any value. This allows container images or services to set the value for all apps without having to modify configuration for each application. If an app wants to opt out, they can either delete from the env hash, or remove that configuration.
cc/ @rafaelfranca
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
wisetara/wisetara/deprecate-args-ActiveSupport__TestCase#assert_nothing_raised-for-pr
Wisetara/deprecate args active support test case#assert nothing raised for pr
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
creating all databases mutates the connection pool. This patch restores
the connection pool to the connection spec established before creating
all databases. Fixes #23279
|
|\ \ \
| | | |
| | | | |
Add `internal` attribute to routes
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is meant to provide a way for Action Cable, Sprockets, and possibly
other Rack applications to mark themselves as internal, and to exclude
themselves from the routing inspector, and thus `rails routes` / `rake
routes`.
I think this is the only way to have mounted Rack apps be marked as
internal, within AD/Journey. Another option would be to create an array
of regexes for internal apps, and then to iterate over that everytime a
request comes through. Also, I only had the first `add_route` method set
`internal`'s default to false, to avoid littering it all over the
codebase.
|
| | | | |
|
| | | | |
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | | |
We should be able to pass options to minitest via TESTOPTS environment
variable
|
| | |
| | |
| | |
| | | |
Get it? ( ͡° ͜ʖ ͡°)
|
|\ \ \
| | | |
| | | | |
use method provided by minitest
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
The process of converting `Test` to `String` is already defined in minitest.
I think it is better to use that for the consistency of output content.
ref: https://github.com/seattlerb/minitest/blob/master/lib/minitest/test.rb#L261..L267
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Having collection caching that wraps templates and automatically tries
to infer if they are cachable proved to be too much of a hassle.
We'd rather have it be something you explicitly turn on.
This removes much of the code and docs to explain the previous automatic
behavior.
This change also removes scoped cache keys and passing cache_options.
|
|\ \
| | |
| | | |
move digest cache on to the DetailsKey object
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This moves digest calculation cache on to the details key object.
Before, the digest cache was a class level ivar, and one of the keys was
the hash value of the details key object:
https://github.com/rails/rails/blob/13c4cc3b5aea02716b7459c0da641438077f5236/actionview/lib/action_view/digestor.rb#L28
An object's hash value is not unique, so it's possible for this cache
key to produce colliding keys with no resolution. This commit move
cache on to the details key object itself, so we know that the digests
are always unique per details key object.
|