amberframework/granite

create and update should be able to take a hash

watzon opened this issue · 3 comments

Seeing as they takes the **args and converts it into a hash anyway, it would be ideal if they could just take a hash.

Related: #370.

Wait, am I stupid? The create and update methods just pass the **args into create(args.to_h) and update(args.to_h), so they must already be available in a form that takes a hash, right?

@watzon makes total sense to me, I would expect this kind of behavior since it makes creating objects from data you collect during run-time.