Good point. I guess that would work for 1 domain object: users. But the
whole approach for modifying the JSON-serialization should work for
multiple view-methods with different model-classes. E.g.:
def get_own_user(request):
...
def get_posts(request):
...
def get_something_else(request):
...
For each view, I need to attach a different marshmallow-schema. That
wouldn't work with my own renderer, right? Unless I define a different
renderer for every single serialization, which doesn't seem right.
Am Samstag, 6. Juni 2015 19:52:32 UTC+2 schrieb Jonathan Vanasco:
>
> What about defining your own renderer, and using that in viewconfig
> instead of json?
>
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
