seanohalpin’s Activity (RSS)

Fwiw, I'm also poking at a few type constraint systems and hope its possible to have some kind of adapter class that allows using these type constraints under d...

I initially thought perhaps I could get away with something like:

  require 'doodle'

  class TypeCheck
    def TypeCheck.fixed_length(length)
      ["be leng...

My examples were pretty screwed up, here is a cleaned up version with example:

    require 'doodle'

    $counter = 0

    class Foo < Doodle
       has init_a...

oh and the first block should of course have read:

    f.has?(:simple_attr)       # => true
    f.valued?(:simple_attr)    # => false
    f.assigned?(:simple_a...

I've been mulling over this for some days, but for these cover the really essential introspection needs. The only possibly relevant one that's possibly missing ...

I like #has?

obj.has?(name) would be syntactic sugar for
obj.doodle.attributes.key?(name) where obj can be either a class or an
instance.

I'll include this in t...

The clearer is great, that really complements the <.assigned?>

I agree that the ActiveRecord way is ugly for it really conflicts with the way you'd expect boole...

I see I didn't really state my intentions clearly. What I was looking for was something along the lines of lazy initialization. And neither nor really do that.

...

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 simulat...

document #assigned? and #clear!

document readonly

As you have pointed out, #instance_variable_defined? and #remove_instance_variable do exactly what you want.

However, using them does rely on the underlying imp...

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 tho...

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

require 'doodle'

class Foo < Doodle
  counter = 0
  has :uid, :readonly => true do
    init { counter ...

Apologies for the long delay in replying.

For your use case, I would use #init rather than #default. Something like this:

require 'doodle'

class Foo < Doodle
...

Oh, and here is the way to currently work around this:

class Foo < Doodle
  @@serial = 0
  has :uid do
     default{ @uid = @@serial += 1 }
  end
end

x = Foo....

It would be nice if one could easily prevent the generation of the setter method. Perhaps something along the lines of Moose's 'is' property:

has :uuid, :is =>...

I used Moose under perl and there they used the concept of 'predicate' and 'clearer' methods (normally something like: has_X and clear_X). A predicate under rub...

Currently the default behaves like a "if no value is set, return the (result of) default". So requesting the same attribute,that has no value, multiple times wi...

don't use eval to define collectors in 1.9

make it possible to define mutually exclusive attributes, i.e. either/or

make it easy to define your own visitors

and redo to_hash to use this (rather than current hack with to_yaml)

update docs to - sort out examples (use better examples) - ensure that all core functionality is documented

Not needed anymore - works as expected with modules (e.g. can do Foo::Bar(args) as well as Foo.Bar(args)

perhaps integrate with ditz

Command line tool to

• add ticket
• change ticket state
• close ticket
• list tickets

e.g. explain how to use in modules and limitations

document how to use defer_validation to change attributes, even when that leaves the doodle temporarily in an invalid state

For example, I want to use something like:

  has :shapes, :collect => [Circle, Square]

or

  has :shapes, :collect => {:circle => Circle, :square => Squar...

Add Doodle.from_json for parsing JSON and doodle.to_json for output