| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Rename local variable name `current_user` to `verified_user` [ci skip]
|
|/
|
|
|
| |
Assigning local variable named `current_user` in the condition is
confusing.
|
|
|
|
|
|
|
| |
This reverts commit 296d024b4e91c4891ae0b010249193513e63b921, reversing
changes made to e341d835070c7ef9990f41e02bbf46536be0aee7.
We aren't trying to compare to current_user, we're assigning that variable.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
config.time_zone is no longer in included in config/application.rb.
See 28dcadc0140dfdebe87d5e691fd709c0a9ae0bae.
|
| | |
|
|\ \
| | |
| | | |
Update Action Cable README.md - typo fix [ci skip]
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Fix doc format for `duplicable?` [ci skip]
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
Remove unnecessary ruby version comments
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
rachel-carvalho/update_browser_compatibility_for_http_verbs
Update guide to reflect browser compatibility for HTTP verbs
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Additional explanation about cache implementations
|
|/ / |
|
|\ \
| | |
| | | |
Bump Travis ruby version to 2.4.1
|
| | |
| | |
| | |
| | | |
https://www.ruby-lang.org/en/news/2017/03/22/ruby-2-4-1-released/
|
|\ \ \
| | | |
| | | | |
Fix duplicable? for Rational and Complex on ruby master, since they are now duplicable
|
| | | |
| | | |
| | | |
| | | | |
duplicable
|
|\ \ \ \
| |/ / /
|/| | | |
Move comment to inside the method [ci skip]
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Because this comment is not document for `supports_ranges?`
ref: https://github.com/rails/rails/pull/27636#discussion_r107560081
|
|\ \ \
| | | |
| | | | |
Remove `CollectionProxy#uniq`
|
|/ / /
| | |
| | |
| | |
| | | |
Since #28473 `uniq` is delegated to `records`, so `CollectionProxy#uniq`
is unnecessary.
|
|\ \ \
| | | |
| | | | |
Document AC::Connection::Authorization#reject_unauthorized_connection
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This method is repeatedly used throughout the docs (in the [AC::Connection docs](https://github.com/rails/rails/blob/12b684985837bc8ee9ad15c174cf4e07ca82d7c4/actioncable/lib/action_cable/connection/base.rb#L28), the [AC README](https://github.com/rails/rails/blob/12b684985837bc8ee9ad15c174cf4e07ca82d7c4/actioncable/README.md#a-full-stack-example), the [AC Guides](https://github.com/rails/rails/blob/12b684985837bc8ee9ad15c174cf4e07ca82d7c4/guides/source/action_cable_overview.md#connection-setup)), but not actually documented itself and seemingly not supported for public use based on its current `private` status.
This actually makes the method public and documents it. The actual behavior that’s documented here is implemented [here](https://github.com/rails/rails/blob/12b684985837bc8ee9ad15c174cf4e07ca82d7c4/actioncable/lib/action_cable/connection/base.rb#L213-L219), via [this rescuing of the UnauthorizedError](https://github.com/rails/rails/blob/3dd1de8ba4d5862b01e7f5dd3878b21fd98b443b/actioncable/lib/action_cable/connection/base.rb#L172).
The method is [already tested here](https://github.com/rails/rails/blob/25473baf409185638073fe2f016f4b9dda284e50/actioncable/test/connection/authorization_test.rb#L17-L29).
|
|\ \ \ \
| | | | |
| | | | | |
List options for `rails new --webpack=WEBPACK`
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When you type `rails new -h`, the `--database=DATABASE` options display
this useful message:
> Preconfigure for selected database (options: mysql/postgresql/sqlite3/oracle/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
However, the `--webpack=WEBPACK` option only displays this:
> Preconfigure for app-like JavaScript with Webpack
so it's hard to know *which* values are valid for `WEBPACK`.
This commit improves the help message to display:
> Preconfigure for app-like JavaScript with Webpack (options: react/vue/angular)
The implication of this commit is that the list needs to be manually updated
whenever rails/webpacker adds support for a new framework.
However, I don't imagine this list to change very frequently, and I think that
the benefit of display the list to the users is greater than the hustle of
updating the list when needed.
|
| | | | |
| | | | |
| | | | |
| | | | | |
[ci skip]
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Change AD::ParamsParser::ParseError deprecation so it can be rescued
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes #28525
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
An alternative to DeprecatedConstantProxy which works more transparently
with exceptions because it returns the object that the new constant
refers to rather than a proxy. This is then compatible with
`rescue OldException`.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Correctly reset ARGV for "rails runner `CODE' arg arg arg..."
|
| | | | | | | |
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The code itself should not be in the ARGV vector.
Fixes #28515
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
CLI arg "host" has precedence over ENV var "host"
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This is a regression from when the server command switched to its own
argument parser, as opposed to Rack's. Rack's argument parser, when
provided with a "host" argument, gives that value precedence over
environment variables.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Fix `LogSubscriber` to allow legacy `binds`
|
| | |/ / / / /
| |/| | | | |
| | | | | | |
| | | | | | | |
Follow up of #27939.
|
|\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | | |
Don't add a dummy API key to every new Rails app
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Every new Rails app is currently generated with
`Rails.application.secrets[:api_key]` set to `123`.
This comes from a line in `config/secrets.yml` that, in my opinion,
should be left commented out to only serve as a syntax example, rather
than being actually set in every Rails app.
Additionally, we might want to give a better example than `123`, since
in the same file we are suggesting to
> Make sure the secret is at least 30 characters and all random,
> no regular words or you'll be exposed to dictionary attacks.
The result of this commit is that `config/secrets.yml` will include something like:
```yaml
# Shared secrets are available across all environments.
# shared:
# api_key: f56930851993982510d5bd9236f4108f6fe7c15448f1c6923a51872e0dbae1a24d274b318abb6518b540dfb51079c61640885f607467e5ed1053849be7587d61
```
rather than this:
```yaml
# Shared secrets are available across all environments.
shared:
api_key: 123
```
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
Fix `assert_logged` failure
|
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | | |
`'#{name}' file doesn't exist, so no dependencies` was removed in
bb04814.
|
| | | | |
| | | | |
| | | | |
| | | | | |
[ci skip]
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
y-yagi/dont_comment_out_file_watcher_during_rails_upgrade_process
Don't comment out config.file_watcher during Rails upgrade
|
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is necessary only when updating to Rails 5.0, it is not necessary
for updating to 5.1.
Related #24243
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Suppress `WARNING: nonstandard use of \\ in a string literal` warning
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
by setting `escape_string_warning = off`
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Tried to make the sentence read more clearly.
[ci skip]
|