Seanohalpin doodle

Comments and changes to this ticket

• 

  Sean O'Halpin October 11th, 2009 @ 02:34 AM

  • State changed from “new” to “resolved”

  Use the :readonly option (introduced in version 0.1.9):

  require 'doodle'
  
  class Foo < Doodle
    counter = 0
    has :uid, :readonly => true do
      init { counter += 1 }
    end
  end
  
  bar = Foo.new
  bar.uid                         # => 1
  bar.uid = 2
  # ~> -:12: Trying to set a readonly attribute: uid (Doodle::ReadOnlyError)
  

  Hmmm. I've had a look at the documentation and found that :readonly is not documented. Also, it fails to protect overwriting in certain edge cases (e.g. when you use #defer_validation).

• 

  Sean O'Halpin October 11th, 2009 @ 02:37 AM

  Regarding your other points:

  By all means tag a ticket with "feature" to denote a feature request.

  I'd welcome any patches - no promises to incorporate them though ;)

• You flagged this item as spam.
  

  Justin Ossevoort October 12th, 2009 @ 08:03 AM

  Ah I was wondering how to do that, I'm more used to traditional issue tracking systems which have a clear classification, but I can see how tags help to simulate this ;-)

  And great that the <:readonly> flag was already present, I guess I should have studied doodles core more ;-)