| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \
| | | |
| | | | |
[ci skip] Fix rails_command comments
|
| | |/
| |/| |
|
| |/
|/| |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When generating models, we created ApplicationRecord in the default
location if no file existed there. That was annoying for people who
moved it to somewhere else in the autoload path. At this point, the
vast majority of apps should have either run the upgrade script or
generated a model since upgrading. For those that haven't the error
message after generating a new model should be helpful:
NameError: uninitialized constant ApplicationRecord
To ease friction in that case, this also adds a generator for
ApplicationRecord.
|
|
|
|
|
|
|
| |
Generators need to be aware of namespace to work properly in engines.
Methods to help with this lived in Rails::Generators::NamedBase. Moving
them to Rails::Generators::Base (which NamedBase inherits from) allows a
follow-up in which a namespace aware unnamed generator can be created.
|
|
|
|
|
|
| |
Bootsnap precomputes load path resolution and caches ruby ISeq
and YAML parsing/compilation, reducing application boot time by
approximately 50% on supported configurations.
|
| |
|
|\
| |
| | |
Do not generate unused components contents in `app:update` task
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, `app:update` generates all contents regardless of the
component using in application.
For example, even if not using Action Cable, `app:update` will generate
a contents related to Action Cable. This is a little inconvenient.
This PR checks the existence of the component and does not generate
unnecessary contents.
Can not check all options in this way. However, it will be able to
prevent the generation of unnecessary files.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Abstract boolean serialization has been using 't' and 'f', with MySQL
overriding that to use 1 and 0.
This has the advantage that SQLite natively recognizes 1 and 0 as true
and false, but does not natively recognize 't' and 'f'.
This change in serialization requires a migration of stored boolean data
for SQLite databases, so it's implemented behind a configuration flag
whose default false value is deprecated. The flag itself can be
deprecated in a future version of Rails. While loaded models will give
the correct result for boolean columns without migrating old data,
where() clauses will interact incorrectly with old data.
While working in this area, also change the abstract adapter to use
`"TRUE"` and `"FALSE"` as quoted values and `true` and `false` for
unquoted. These are supported by PostreSQL, and MySQL remains
overriden.
|
| |
|
|
|
|
|
|
|
|
| |
Rather than protecting from forgery in the generated
ApplicationController, add it to ActionController::Base by config. This
configuration defaults to false to support older versions which have
removed it from their ApplicationController, but is set to true for
Rails 5.2.
|
| |
|
|\
| |
| | |
Add system tests to generate scaffold
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The `capify` command has been removed by Capistrano 3 and became to
`cap install`.
Therefore, the `capify!` method has no meaning in Capistrano 3.
I think that should deprecate.
Ref: https://github.com/capistrano/capistrano/commit/492793916acf32ffe1604daec6fd4892c8935018
|
| | |
|
|\ \
| | |
| | | |
Drop IRB out of the web-console Gemfile comment
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We don't provide exactly the same experience as IRB does, so let's not
advertize it like that. We can say that it's an interactive console,
without further references. I have also followed byebug's comment and
changed the calling `console` part. Hopefully, this can hint that the
invocation is not view specific and you can use it like the debugger
statement.
[ci skip]
|
|\ \
| |/
|/| |
Default Message Encryptor Cipher to AES-256-GCM From AES-256-CBC
|
| |
| |
| |
| | |
- Introduce a method to select default cipher, and maintain backward compatibility
|
|/ |
|
|\
| |
| |
| |
| | |
orhantoy/feature/fix-scaffold_controller-generator-usage
[ci skip] Fix `scaffold_controller` generator usage
|
| | |
|
| |
| |
| |
| | |
We don't get any benefit from it at all.
|
|\ \
| | |
| | |
| | |
| | | |
greysteil/better-spacing-in-production-environment
Better spacing in environments/production.rb file
|
| | |
| | |
| | |
| | |
| | | |
Previously there were a couple of places where double-spacing or no spacing
was happening, depending on skipped options.
|
| | | |
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Allow a default value to be declared for class_attribute
* Convert to using class_attribute default rather than explicit setter
* Removed instance_accessor option by mistake
* False is a valid default value
* Documentation
|
| |
| |
| |
| |
| |
| | |
secrets key file that is created by rails secrets:setup"
This reverts commit 75500476eb7e953a06cc64e67ecc57b13ef8cc99.
|
|\ \
| | |
| | | |
[ci skip] Add elm option of webpack to generator description
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
AEAD encrypted cookies and sessions
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit changes encrypted cookies from AES in CBC HMAC mode to
Authenticated Encryption using AES-GCM. It also provides a cookie jar
to transparently upgrade encrypted cookies to this new scheme. Some
other notable changes include:
- There is a new application configuration value:
+use_authenticated_cookie_encryption+. When enabled, AEAD encrypted
cookies will be used.
- +cookies.signed+ does not raise a +TypeError+ now if the name of an
encrypted cookie is used. Encrypted cookies using the same key as
signed cookies would be verified and serialization would then fail
due the message still be encrypted.
|
| | |
| | |
| | |
| | | |
Fixes #29247
|
| | | |
|
|\ \ \
| | | |
| | | | |
Define path with __dir__
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
".. with __dir__ we can restore order in the Universe." - by @fxn
Related to 5b8738c2df003a96f0e490c43559747618d10f5f
|
|\ \ \
| | | |
| | | | |
Make `secrets:edit` run `secrets:setup` if it hasn't already.
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
Setup config/secrets.yml.enc with template contents for people to edit.
Then generate encryption key and encrypt the initial secrets.
|
| | |
| | |
| | |
| | | |
with it
|
|/ / |
|
| | |
|
|/ |
|
|
|
|
|
|
| |
Capybara 2.14.0 was released. Loosen the tight constraint in the
generated Gemfile, so that Rails applications can take advantage of the
new version
|