and that they get moved into the envelope, if it exists
Conflict is useful to have since it's the (I think) most logical way to represent an e.g. username conflict. Gone is just weird to me that it exists, so I added it because I was there
This propagates them to the response envelope without needing to subclass Resource
…returning None, which the Resource object will then turn into an empty dict.
…s, which themselves are callable)
…iews * 'views' of github.com:pbs-education/django-piston: Added nested destination support.