| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Hstore no longer needs additional quoting to be used in an array, the
array type handles it sufficiently.
|
|\
| |
| | |
Use the type object when sending point columns to the DB
|
| | |
|
|\ \
| |/
|/| |
Don't encourage usage of `columns_hash`
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As discussed in https://github.com/plataformatec/simple_form/pull/1094,
we should not encourage usage of `columns_hash`, and instead provide an
alternate method to determine whether or not an attribute exists.
The language `attribute` was chosen over `column` since these are in the
`AttributeMethods` module.
|
|\ \
| | |
| | | |
Use `Hash#transform_values` to clean up `AttributeSet`
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Use the type object for sending JSON to the database
|
| |/ |
|
|\ \
| |/
|/| |
Add `Hash#map_values` to ActiveSupport to simplify a common pattern
|
|/
|
|
|
| |
Didn't get a chance to convert existing code, I'll skim through the code
base to make use of this later this afternoon.
|
| |
|
|
|
|
| |
[ci skip]
|
|\
| |
| | |
Rename options param of #time_ago_in_words to match API change
|
| |
| |
| | |
Rename `include_seconds_or_options` to `options` to match 6b9356a (which removed the deprecation introduced by #6077). This has no functional impact because the parameter is passed directly through, but makes it clearer that the parameter no longer supports a boolean as input.
|
|\ \
| | |
| | | |
Always pass a column with a cast_type to quote
|
| |/
| |
| |
| |
| |
| |
| |
| | |
The only case where we got a column that was not `nil`, but did not
respond to `cast_type` was when type casting the default value during
schema creation. We can look up the cast type, and add that object to
the column definition. Will allow us to consistently rely on the type
objects for type casting in all directions.
|
|\ \
| | |
| | | |
Add punctuation and fix capitalization in Getting Started guide
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix more small grammar mistakes in the [Getting Started guide](http://edgeguides.rubyonrails.org/getting_started.html#security), in sections 9 and 10.
Specifically, within sections 9.1 “Basic Authentication”, 9.2 “Other Security Considerations”, and 10 “What's Next?”.
“Rails Guides” is generally capitalized on the site, including on the linked page and in the title of the site, so I capitalized it.
“The” is not part of the name of the Ruby on Rails Security Guide – “The” is not in the title on that page.
And I added a missing period and a missing colon at the ends of two sentences.
|
|\ \
| |/
|/| |
[ci skip] Fix router option reference in 4.2 release notes.
|
| | |
|
|\ \
| | |
| | | |
[Postgresql tests] remove duplicate helper
|
| | | |
|
|\ \ \
| |/ /
|/| | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit cede0363830e28e73feafc662eccae7d1db526bb.
Reason: CHANGELOG should not be updated on docrails
|
| | | |
|
|\ \ \
| | | |
| | | | |
Update the levenshtein distance method in guides.
|
| | |/
| |/| |
|
|\ \ \
| |/ /
|/| | |
Add missing period in Getting Started guide
|
|/ /
| |
| |
| | |
Within section 5.10 Adding Some Validation
|
|\ \
| | |
| | | |
MySQL doesn't work with foreign keys
|
|/ /
| |
| |
| |
| |
| | |
This was previously fixed in e84799d but broken in 3f596f8. This commit
reintroduced the conditional that prevents the foreign keys from being
added to MySQL databases.
|
|\ \
| | |
| | | |
Fix test with `add_foreign_key` DSL
|
|/ / |
|
|\ \
| | |
| | |
| | | |
rename primary key sequence only if it exists
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
Always instrument ActiveSupport::Cache
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The current approach is broken because it uses a thread local value
which means on multi-threaded environments it has to be turned on
per thread. Secondly, ActiveSupport::Notifications does not
instrument items when there are not subscribers so this flag is
unnecessary.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add always permitted parameters as a configurable option.
[Rafael Mendonça França + Gary S. Weaver]
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* General style fixes.
* Add changes to configuration guide.
* Add missing tests.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* This commit adds back the always_permitted_parameters
configuration option to strong paramaters.
* The initial pull requests where this feature was added
are the following:
- https://github.com/rails/rails/pull/12682
- https://github.com/rails/strong_parameters/pull/174
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Update documentation for run_callbacks
|
| | | | | |
| | | | | |
| | | | | | |
In some cases run_callbacks will return nil. I'm attempting to update the documentation for the method to clarify.
|
|/ / / / / |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Leave the note for `ActiveModel`, since it can't yet detect mutations
(hopefully we can change this in time for 4.2). However, we now detect
mutations on all supported types in `ActiveRecord`, so we can note that
`_will_change!` is no longer needed there.
|
| | | |
| | | |
| | | |
| | | | |
Closes #15942
|