Parameterized blueprints about machinist HOT 4 CLOSED

Hmmm, not sure. It'd be a mess to implement on top of the current named blueprints and caching mechanism.

I'd rather find some way to pass stuff like this in as extra arguments, but I'm not sure how to fit that in with the existing arguments to make.

from machinist.

Are you thinking something like:

Post.blueprint(:with_comments, :blueprint_params => [:num_comments]) do |params|
  # ...
  comments(params[:num_comments].to_i)
end

Post.make(:with_comments, :num_comments => 3)

That syntax for making the objects feels less clear to me. Keeping pecs/tests as clear and concise as possible is paramount for me. However, having this functionality is more important than the syntax. If you have a strong preference i am open to implementing that.

I haven't looked at the internals of the caching mechanism yet. I'll take a look soon an see if i can see an approach to caching the results of parameterized blueprints.

from machinist.

the randexp gem would work great for this, check it out

from machinist.

The caching mechanism is now gone, but this still all feels a bit too magic to me. I'd just make some nice helper methods that wrap calls to Machinist if I was doing the same thing.

That said, feel free to fork and give it a go. You may come up with something that surprises me, and even if you don't, there's no harm in having a fork that meets your needs.

Or you can always make another gem that extends Machinist. (I'm encouraging the guys working on DataMapper support to make a machinist-dm gem, for example.)

from machinist.