What about making the polymorphic routing in rails to try a plural route
first. If it fails, try a singleton route. If it fails, raise.
This is not the nicest and most performant way (the result could be
cached in production so it doesn't really matter in the end) but I guess
it should solve
Is there somewhere a list of names that should not be used as action names ?
I recently created an action named load and it disappeared from inherited
controller.
Would such a list be equal to : AbstractController::Base.internal_methods ?
Robert Pankowecki
http://robert.pankowecki.pl
--
You
I was thinking about the same thing too, but something was blocking me at
that moment. Do you mind digging into the source code and see if it's
possible from your perspective, and then send a pull request if you can
patch it?
Thanks a lot! :)
On Wed, Jul 13, 2011 at 3:20 AM, Corin Langosch
On 13 Jul 2011, at 08:20, Corin Langosch wrote:
What about making the polymorphic routing in rails to try a plural route
first. If it fails, try a singleton route. If it fails, raise.
This is not the nicest and most performant way (the result could be cached in
production so it doesn't
ORLY? I didn't see that ticket. Lemme have a look!
On Wed, Jul 13, 2011 at 7:50 AM, Andrew White an...@pixeltrix.co.uk wrote:
On 13 Jul 2011, at 08:20, Corin Langosch wrote:
What about making the polymorphic routing in rails to try a plural route
first. If it fails, try a singleton route.
This fails for me on Rails 3.0.9 and Rake 0.9.2
gems/railties-3.0.9/lib/rails/commands/plugin.rb:277: Commands is not a
module (TypeError)
Using bundler
This issue is currently being discussed
https://github.com/rails/rails/issues/1866
IMO this is more of rake issue, although it could
On Wed, July 13, 2011 04:56, Robert Pankowecki wrote:
Is there somewhere a list of names that should not be used as action
names ?
I recently created an action named load and it disappeared from
inherited
controller.
Would such a list be equal to :
Can you change something in this kind of relationship, because it
works great in previous version?
NameError (uninitialized constant User::Post)
class Post ActiveRecord::Base
belongs_to :user
...
class User ActiveRecord::Base
has_many :posts
accepts_nested_attributes_for :posts
...
Please ask this question on Rubyonrails-talk. It seems like you are defining
your Post model in a file incorrectly named / located.
On 13/07/2011, at 22:04, M Bougie mathi...@socialship.net wrote:
Can you change something in this kind of relationship, because it
works great in previous
