You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This refactoring attempts to make better use of existing Represntable
idioms, such as `representation_wrap`.
API changes:
* `id` property is automatically defined for a resource.
* resource attributes should be specified in `attributes` block.
* `has_one` and `has_many` now support `decorates:` option (in other
words, no longer confined to Inline Representers)
Closes#11
Signed-off-by: Alex Coles <alex@alexbcoles.com>
This refactoring attempts to make better use of existing Represntable
idioms, such as `representation_wrap`.
API changes:
* `id` property is automatically defined for a resource.
* resource attributes should be specified in `attributes` block.
* `has_one` and `has_many` now support `decorates:` option (in other
words, no longer confined to Inline Representers)
Closes#11
Signed-off-by: Alex Coles <alex@alexbcoles.com>
From @caseymct on January 8, 2016 4:16
as per glitter chat:
I have an Event model that
has_one
host, a User. the User model has it's own (quite large) decorator. It would be great to haveI'd like to avoid doing
and duplicating this in every decorator that has a user.
Copied from original issue: trailblazer/roar#182
The text was updated successfully, but these errors were encountered: