Here's a simple way to avoid having to specify all the params.
User.columns.*.name - %w{created_at updated_at crypted_password
key_timestamp remember_token remember_token_expires_at salt}
Somewhat ugly but should work. Then you can either make two creators (one
invite, one new), or...
make one, make an attr (not a field) to hold the state destination, have the
attr in the params, add logic to the block or to the become proc to set it
and have a test as to what email or whether to send an email at all in the
create block.
I'd recommend the first option.
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/hobousers/-/585Nlhzqwx0J.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/hobousers?hl=en.
