| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ /
| |
| |
| |
| | |
Lets have the server and the Rake task go through the same ropes, so we can
share all the file lookup, adding, and deleting code.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
If we're gonna do this right, it will look mighty different from this anyway.
(Looking at you, Rails 5.1).
It isn't being used in any code as of now, so yanking is the best option.
|
| |
| |
| |
| | |
References https://github.com/rails/homepage/issues/46.
|
| | |
|
|\ \
| | |
| | | |
Remove passing `with_dispatchers` to AppGenerator
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- While working on https://github.com/rails/rails/pull/22790 I found out
that we pass `with_dispatchers: true` but it's not used at all by Rails.
- We were passing `with_dispatchers: true` in few tests too but again
it's not used by Rails.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit comes from the comments made by @matthewd at https://github.com/rails/rails/pull/23795/files#r54469637
and by @rafaelfranca at https://github.com/rails/rails/pull/23795/files#r54609364
The idea is that if you type (for example) "rake db:migrate" in an AppGenerator,
then this should actually invoke `rake db:migrate` on the command line, whereas
if you type "rails_command db:migrate", this should invoke `rails db:migrate`.
|
|\ \ \
| | | |
| | | | |
Remove redundant regexp escapes in generators
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Advertise the console web-console feature
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In the latest version of Web Console, you can call `console` anywhere in
your application and get a console with that binding in it. I think this
is worth advertising, as it may be useful to do outside of controllers
and views.
[ci skip]
|
|/ / / / |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Between major versions 2 and 3, we hit a bug. It's fixed in version 3,
however, the explicit 2.x requirement of `~> '2.0'` will prevent people
from getting the fix with `bundle update` and they would have to
explicitly set the constraint to `~> '3.0'`.
For more information see: rails/web-console#178.
I propose we drop the explicit version constraints in the Gemfile. Web
Console has been relatively stable for the past couple of years, and I
don't anticipate any major alterations, like we saw between major
versions 1 and 2.
|
|\ \ \
| | | |
| | | | |
Fixed semantics of couple of tests in the configuration_test.rb [ci skip]
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
i18n fallbacks test fixes
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
using map
- Fixed test name for setting fallbacks to config.i18n.fallbacks = [{ :ca => :'es-ES' }]
|
| | | |
| | | |
| | | |
| | | | |
Reads much better doesn't it.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Stuff I see in passing while I am doing a walkthrough.
See rationale in 5b8738c.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Stuff I see in passing while I am doing a walkthrough.
See rationale in 5b8738c.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Stuff I see in passing while I am doing a walkthrough.
See rationale in 5b8738c.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Stuff I see in passing while I am doing a walkthrough.
See rationale in 5b8738c.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
y-yagi/remove_unnecessary_config_in_sprockets-rails-3
remove config that are no longer needed in sprockets-rails 3
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
`config.assets.raise_runtime_errors` and `config.assets.digest` are enabled
by default in sprockets-rails 3.
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
Defining paths relative to a file name has always hurt my soul,
with __dir__ we can restore order in the Universe.
|
| | | |
| | | |
| | | |
| | | | |
Follow up to #24050.
|
|\ \ \ \
| | | | |
| | | | | |
using rails dev:cache instead of rake dev:cache in test case
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
[ci skip] correcting test case specifying `rails routes` instead of `rake routes`
|
| | | | | | |
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
of `rake routes`
|
|/ / / /
| | | |
| | | |
| | | | |
Adding period in the end.
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fix description in cookies_serializer.rb being corrupted by gsub when updating
|
| |/ / / |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Remove load_paths file
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
convert cable.coffee to cable.js
|
| |/ /
| | |
| | |
| | | |
In order to eliminate the dependecy of CoffeeScript.
|
|\ \ \
| | | |
| | | | |
Deprecate :controller and :action path parameters
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allowing :controller and :action values to be specified via the path
in config/routes.rb has been an underlying cause of a number of issues
in Rails that have resulted in security releases. In light of this it's
better that controllers and actions are explicitly whitelisted rather
than trying to blacklist or sanitize 'bad' values.
|
|\ \ \ \
| | | | |
| | | | | |
do not set Action Cable's config when specify `--skip-action-cable` option
|
| | | | |
| | | | |
| | | | |
| | | | | |
Also remove duplicated `config.action_cable.url` config.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Delete CTRL-C message as is duplicates Puma
|
| | | | | | |
|
| | | | | | |
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These should allow external code to run blocks of user code to do
"work", at a similar unit size to a web request, without needing to get
intimate with ActionDipatch.
|