| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | | |
|
|\ \ \ \ \ \ |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
When setting an array column (or other PostgreSQL-specific data type)
to be validated for uniqueness, the resulting SQL query is generated with
syntax errors, like this:
SELECT 1 AS one FROM "postgresql_arrays"
WHERE "postgresql_arrays"."nicknames" = '["john", "johnny"]' LIMIT 1
This happens because Ruby Arrays must be type-casted to their PostgreSQL
equivalent. This small patch fixes this issue, calling the adapter's
type_cast method.
Closes #8077
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
It's not necessary to use this extension here, we are fine with Array#unshift.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Cleanup some code, avoid extra hash with reverse_merge, and don't use
send for :id, since it's always present.
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
Fixes: #8075.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Remove/add ; where necessary, fix indentation.
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
handle protocol option in stylesheet_link_tag and javascript_include_tag
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
closes #8388
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Format routes as html on debug page
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When someone gets a routing exception, the routes are rendered (starting in Rails 4.0). This PR brings parity between the html routes in the `rails/info/routes` path and when rendered from an exception. This is the continuation of #8521 which brought html formatted routes.
In addition to bringing parity to the two views, we're keeping our views DRY by rendering off of the same partials. In this case Railties depends on partials provided by ActionDispatch. I'm open to alternative implementations. Ideally both views will use the same code so any improvements or updates to it will be reproduced on both.
<hr />
![](http://f.cl.ly/items/3O1D0K1v0j0i343O3T3T/Screen%20Shot%202012-12-17%20at%203.07.20%20PM.png)
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
AR supporting new int4range and int8range data type on PostgreSQL >= 9.2. Fix #8528 pull request
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Fix realization
|
| |\| | | | | |
| | | | | | | |
| | | | | | | | |
AR supporting new int4range and int8range data type on PostgreSQL >= 9.2
|
| | | |_|_|/ /
| | |/| | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
HTML formatting to Rails::InfoController#routes
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This PR adds formatting and meta-data to the display of the internal routes. Users can now toggle between showing helpers with the `_path` or _`url` suffix.
There are multiple ways to achieve this, this method uses partials for formatting and meta-data. The partials can be re-used when rendering `routing_error.erb`, though that will need to be in a separate PR.
![](http://f.cl.ly/items/3A2p3c1T1t2f2X2R2K2S/Screen%20Shot%202012-12-12%20at%202.28.01%20PM.png)
ATP Railties
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
directory structure and load path
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The conditional_layout? method is not for public use and doesn't
actually do what the documentation suggested it does. It's actually
used to determine whether or not to use the explicit layout definition
defined in a controller or use the implicit layout definition.
Also documentation was added for the action_has_layout? method which
acts as a master switch for disabling the layout for the current
action. This method was added so that action caching didn't depend
on accessing layout internals but is also used by third-parties,
most notably the [Hobo][1] application.
[1]: https://github.com/hobo/hobo
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Add nodoc to AS::BasicObject [ci skip]
|
|/ / / / / / / |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Add missing requires to core_ext/integer/time
|
|/ / / / / / / |
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
DebugExceptions `File.join` => `File.expand_path`
|
| | | | | | | |
|
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | | |
Somehow this got lost in my PRs before. I'm going to re-check all the
guides to make sure this didn't happen again elsewhere.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Properly deprecate AS::BasicObject without breaking subclasses of it
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
absence of attributes.
Add `ActiveModel::Errors#add_on_present` method. Adds error messages to present attributes.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Remove blank lines from generated Gemfile
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
Introduced by 059bdc3415b0f1fb436c56a399a41b90fe3e87f0
|
| |_|_|/ / /
|/| | | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
actionpack/lib/action_view/helpers/form_helper.rb
railties/lib/rails/info_controller.rb
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit d1e70cb7b410f5151b08af9b38b2d6d80c1c61c2.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 2f0311d79af01dc59ab3bd95cd6a56511258f917.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit db9b619f2851d7aeef9b239f6c19d0076faf5909.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit e5f8b2be64a74ce05e7c8b873d3e795e7bc68df5.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 6e72099a382c9731c7b40aa1b10237318e31ac92.
Reason: Feel that this isn't the right place.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Since Rails 3.1, change method is preferred for writing
migrations. Updated the example, because that command
would generate migration with change method.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
https://github.com/lifo/docrails/commit/55a2820cc6d33e96b8d1b64b38b033913058dce4
messes up
https://github.com/lifo/docrails/commit/cfd324b4b68469ba3188e4b7ba8586e59b239693
Hopefully there is other stuff lost in translation...
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
application.
|
| | | | | | |
|
| | | | | | |
|