- 18 12月, 2015 35 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Kasper Timm Hansen 提交于
Document when fallback_location is used [ci-skip]
-
由 Rafael França 提交于
Fix typo
-
由 Akshay Vishnoi 提交于
-
由 Rafael Mendonça França 提交于
It will make sure that the generated application in the tests get the gem.
-
由 Matthew Draper 提交于
ActiveRecord::Base#find(array) returning result in the same order as the array passed
-
由 Matthew Draper 提交于
-
由 Matthew Draper 提交于
We know the query will return exactly one row for each entry in the `ids` array, so we can do all the limit/offset calculations on that array, in advance. I also split our new ordered-ids behaviour out of the existing `find_some` method: especially with this change, the conditionals were overwhelming the actual logic.
-
由 Matthew Draper 提交于
Do not include column limit in schema.rb if it matches the default
-
由 Matthew Draper 提交于
Update CHANGELOG.md for readability
-
由 Matthew Draper 提交于
Support passing the schema name prefix to `conenction.indexes`
-
由 Matthew Draper 提交于
Ignore index name in `index_exists?` when not passed a name to check for
-
由 Matthew Draper 提交于
Remove legacy mysql adapter
-
由 Derek Prior 提交于
If you're not familiar with how the `Referer` header works, you likely won't understand why you need to provide a fallback or under what circumstances it would be used. Hopefully this clarifies things a bit.
-
由 Jeremy Daer 提交于
-
由 Guillermo Iguaran 提交于
Remove warnings from actioncable test
-
由 Guillermo Iguaran 提交于
Require Nokogiri >= 1.6.7.1
-
由 Jon Moss 提交于
Many CVEs released: https://groups.google.com/forum/#!topic/ruby-security-ann/aSbgDiwb24s
-
由 Matthew Draper 提交于
Only dup Ruby's Hash and Array.
-
由 Kasper Timm Hansen 提交于
When calling `to_h` on an `ActionController::Parameters` instance it would `deep_dup` its internal parameters. This inadvertently called `dup` on a passed Active Record model which would create new models. Fix by only dupping Ruby's Arrays and Hashes.
-
由 David Heinemeier Hansson 提交于
-
由 eileencodes 提交于
Logging Action Cable to STDOUT caused the development log to see double messages like this: ``` Started GET "/" for ::1 at 2015-12-17 15:21:34 -0500 Started GET "/" for ::1 at 2015-12-17 15:21:34 -0500 Processing by Rails::WelcomeController#index as HTML Processing by Rails::WelcomeController#index as HTML Rendered /welcome/index.html.erb (0.0ms) Rendered /welcome/index.html.erb (0.0ms) Completed 200 OK in 3ms (Views: 1.3ms | ActiveRecord: 0.0ms) Completed 200 OK in 3ms (Views: 1.3ms | ActiveRecord: 0.0ms) ``` Now that Action Cable is part of Rails it doesn't need it's own logger and will log to STDOUT via the local dev server here: https://github.com/rails/rails/blob/master/railties/lib/rails/commands/server.rb
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
-
由 Rafael França 提交于
ApplicationMailer should be generated by default just like every other Application* parent
-
由 Rafael Mendonça França 提交于
-
由 David Heinemeier Hansson 提交于
-
由 Rafael Mendonça França 提交于
-
由 Kasper Timm Hansen 提交于
We call the thread variable accessors on `Thread.current`, which matches Ruby's documentation: http://ruby-doc.org/core-2.2.0/Thread.html#method-i-thread_variable_get Fix these to stay `current` ( ͡° ͜ʖ ͡°)
-
由 Rafael Mendonça França 提交于
-
由 Rafael França 提交于
Expanding the documentation for collection=objects [ci-skip]
-
由 Rafael França 提交于
traditional make sense with `<tt>ActiveSupport::TaggedLogging</tt>`
-
由 Gaurav Sharma 提交于
-
由 Eric Krause 提交于
-
由 Sean Griffin 提交于
Since the attributes API is new in Rails 5, we don't actually need to keep the behavior of `attribute :point`, as it's not a breaking change.
-
- 17 12月, 2015 5 次提交
-
-
由 Abdelkader Boudih 提交于
-
由 Arun Agrawal 提交于
Warnings coming from code and test are removed
-
由 Rafael França 提交于
Clarify thread_mattr_accessor subclass behavior documentation
-
由 Rafael França 提交于
Add actioncable to build step for release
-
由 Nate Berkopec 提交于
[ci skip]
-