| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| | |
Default headers description
|
| |/ |
|
| |
|
|
|
| |
think that a quoted string will be better as it will automatically
escape double-quotes as well
|
| |
|
|
|
| |
after running, git add .
do not need -a option to git commit
|
| |
|
|
|
| |
Correct :error -> :alert, mention FlashHash class, mention that
you're not limited to notices and alerts, clean up.
|
| |\
| |
| | |
Fix rake guides:validate
|
| | |
| |
| |
| |
| | |
If the validation of a guide encounters an exception, inform about it
and continue with the loop to validate the rest.
|
| |/
|
|
| |
This rake task was looking for the output folder in the wrong place.
|
| |
|
|
|
|
|
|
| |
directory; add exception handling"
This kind of changes should go on a pull request instead.
This reverts commit ecae2f0ef0452f8d333525a6aed58e5ab8d3ccb1.
|
| |\ |
|
| | |
| |
| |
| | |
add exception handling
|
| |/ |
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This reverts commit 8cb9460437eddde6952fbebbc969203cd4d00294.
Reason: #7377 was merged and it fixes this behavior.
|
| | |
| |
| |
| | |
Fixed bug in the example code. A bit related to rails issue in
https://github.com/rails/rails/issues/3223
|
| | |
| |
| |
| |
| | |
Make doc output in grouped_options_for_select divider example match
actual output. The options groups were in backwards order of actual.
|
| |\ \
| | |
| | | |
Remind user a good way to generate a secret code [ci skip]
|
| |/ / |
|
| |\ \
| | |
| | | |
AR::Relation#model would be a better API than AR::Relation#klass
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Remove j alias for ERB::Util.json_escape
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
These tests rely on "make_basic_app", which is a faster version that
does not need to create the whole app directory structure.
|
| | | | |
| | | |
| | | |
| | | | |
Avoid output with config option not set when running some tests.
|
| |\ \ \ \
| | | | |
| | | | | |
Improve eager load on Rails
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The new option allows any Ruby namespace to be registered and set
up for eager load. We are effectively exposing the structure existing
in Rails since v3.0 for all developers in order to make their applications
thread-safe and CoW friendly.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously, ActiveSupport::Autoload was global and reserved
for usage inside Rails. This pull request makes it local,
fixes its test (they were not being run because its file
was named wrongly) and make it part of Rails public API.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The flag was mainly used to add a Rack::Lock middleware to
the stack, but the only scenario the lock is desired is in
development.
If you are deploying on a not-threaded server, the Rack::Lock
does not provide any benefit since you don't have concurrent
accesses. On the other hand, if you are on a threaded server,
you don't want the lock, since it defeats the purpose of using
a threaded server.
If there is someone out there, running on a thread server
and does want a lock, it can be added to your environment
as easy as: `use Rack::Lock`
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously, the eager load behavior was mostly coupled to
config.cache_classes, however this was suboptimal since in
some environments a developer may want to cache classes but
not necessarily load them all on boot (for example, test env).
This pull request also promotes the use of config.eager_load
set to true by default in production. In the majority of the
cases, this is the behavior you want since it will copy most
of your app into memory on boot (which was also the previous
behavior).
Finally, this fix a long standing Rails bug where it was
impossible to access a model in a rake task when Rails was
set as thread safe.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
Clarify and correct the description for the --full option of the
plugin_new generator. [ci skip]
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
generator
|
| | |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
Fix for #5200
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
associations with the same foreign key.
This closes #5200.
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
option_tags coerced to "" instead of nil
Closes #7404
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Refactor AR::Result or inherits. Because we have redundant codes about column_types.
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Change mysql tests for strict mode disabled to work with new sql_mode default in MySQL 5.6.6-m9.
Since this MySQL version, the sql_mode default value is `NO_ENGINE_SUBSTITUTION`.
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Reason since MySQL 5.6.6-m9 the `sql_mode` default value is
`NO_ENGINE_SUBSTITUTION`.
This default parameter change is out of control from Rails.
This test verifies Rails not overriding the default `@@GLOBAL.sql_mode` value
by checking if `@@GLOBAL.sql_mode` is the same as `@@SESSION.sql_mode`.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Fixed some documentation mistakes
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Use instance_accessor: false instead of instance_writer.
|
| |/ / / / / / |
|
