| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
teknofire/fix-using-add_resource-with-a-block-after-gem-call
Fix using add_resource with a block after gem in custom generators
|
| | |/ / /
| | | |
| | | |
| | | | |
generator template.
|
| |\ \ \ \
| | | | |
| | | | | |
Action Cable channel generator doesn't create JS assets if options[:rails][:assets] is false
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | | |
display detailed information in inline reporting
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The errors message only was not displayed, as if it did not use the inline reporting,
modified to also information the method name and the like in error are displayed.
```
# before
Failed assertion, no message given.
bin/rails test test/models/user_test.rb:5
```
```
# after
Failure:
UserTest#test_the_truth:
Failed assertion, no message given.
bin/rails test test/models/user_test.rb:5
```
|
| |\ \ \ \
| |/ / /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
```
Every time when a fixture generate, it’s also generating improper doc.
one: {}
# column: value
#
two: {}
# column: value
```
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
gwincr11/No-Doc-Rails__Generators__Actions__CreateMigration
Add No Doc
|
| | | | | |
| | | | |
| | | | |
| | | | | |
In reference to rails/rail#22403 add a :nodoc:
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Remove blank line generated in config.ru
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Follow the lines of the other `.tt` files ([example](https://github.com/rails/rails/blob/1611ab4db173a7596a7a94c58dabf1483f070304/railties/lib/rails/generators/rails/app/templates/config/environments/development.rb.tt#L26)) that have the space after the
condition to avoid too many white lines in the resulted file.
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In line with the other initializers, add a short comment that explains
what happens when you change the value of the initializer.
[ci skip]
|
| | |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[ci skip]
The initializer has existed since 4.1, for instance see:
https://github.com/rails/rails/blob/v4.1.0/railties/lib/rails/generators/rails/app/templates/config/initializers/cookies_serializer.rb
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
:tada: :beers:
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Our logic is complex now and we don't need to check the version to asset
the behavior so I'm removing the checking here.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
Allow normal version updates within a release series
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We originally chose to apply very strict versioning on the `rails` entry
in the Gemfile, because our future versioning policy was not strongly
defined.
Now it is, and our policy is very much designed on the expectation that
people will regularly update to the latest patch level in their release
series... so we should encourage that.
Of course, Gemfile.lock will do its job and prevent unplanned updates,
just as it does for every other gem in the bundle... but if you run
`bundle update`, we want to get you the latest bug/security fixes
without requiring a manual edit of the Gemfile entry.
Our current version could be a few different shapes, so it takes a bit
of work to find the right specifier, but in principle, we match anything
of the form x.y.*, where x.y matches our current release series.
|
| | | | |
| | | |
| | | |
| | | | |
Still more to do. Please assist!
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
this at a high level
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
```
# before
module Bukkits
class UsersControllerTest < ActionDispatch::IntegrationTest
include Engine.routes.url_helpers
setup do
@user = bukkits_users(:one)
end
```
```
# after
module Bukkits
class UsersControllerTest < ActionDispatch::IntegrationTest
include Engine.routes.url_helpers
setup do
@user = bukkits_users(:one)
end
```
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This file is generated by a gem that is bundled by default in the generated Rails app, just like .sqlite3 files.
Hence it might be natural to be ignored here rather than in each developer's .gitignore_global.
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | | |
Remove legacy mysql adapter
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
ApplicationMailer should be generated by default just like every other Application* parent
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Application* parent
|
| | |/ / / |
|
| |/ / / |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
README.rdoc -> README.md for newly generated plugins
|
| | | | |
| | | |
| | | |
| | | | |
I think Markdown is nowadays a better default.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
prathamesh-sonpatki/kill-extra-line-in-manifest-js
Kill extra newline at the start of generated manifest.js
|
| | | | | | |
|
| | |/ / /
|/| | | |
|
| | | | | |
|
| |/ / / |
|
