Rails Ruby on Rails

Comments and changes to this ticket

• You flagged this item as spam.
  

  Pedro Axelrud March 23rd, 2011 @ 08:02 PM

  I liked the idea, very nice.

• You flagged this item as spam.
  

  Rafael Souza March 23rd, 2011 @ 08:35 PM

  +1, sounds cool for me

  update_attribute sometimes confuses me, I often try to pass a hash for it, mainly when I write some update_attributeS before :)

• You flagged this item as spam.
  

  Juan Maiz (aka João Milho or John Corn) March 23rd, 2011 @ 08:36 PM

  The implementation also seemed very natural.

  Read:
  @foo.bar

  Write:
  @foo.bar=

  Query:
  @foo.bar?

  ... ergo Update: @foo.bar!

  ... looks like the project was asking for an Update module :D

• You flagged this item as spam.
  

  Rodrigo Urubatan March 24th, 2011 @ 12:49 PM

  +1 sounds natural and it is less code to write.

• You flagged this item as spam.
  

  Robson Mendonça March 24th, 2011 @ 01:50 PM

  +1 that's a good feature, much more ruby like.

• You flagged this item as spam.
  

  Nícolas Iensen March 24th, 2011 @ 03:51 PM

  +1 less code and very intuitive

• You flagged this item as spam.
  

  Corey Ward March 24th, 2011 @ 05:39 PM

  -1

  Dropping = is actually counter-intuitive and not very Ruby-like. It's even less Rails-like.

  It's pretty easy to use:

  @foo.bar = 'baz' and @foo.save
  

  Or if you prefer not to have an and (and I can't blame you):

  @foo.set(:bar, 'baz')
  

  Seems pretty straightforward and much shorter, plus it's just an alias for update_attribute.

• 

  Andrew White March 24th, 2011 @ 07:45 PM

  • State changed from “new” to “wontfix”
  • Importance changed from “” to “Low”

  The consensus seems to be that it seems more like a shortcut for updates_attributes!, e.g:

    def foo!(value)
      update_attributes!(:foo => value)
    end
  

  Thanks for the suggestion though.