I see you add it here: 2cb8787

Where is it being used? I could not find any reference.

Hi Valery!

Restea is currenly raising Error and ConfigurationError when there is something wrong in payload request or with fields configured themselves but those are converted into RestError-subclassed exceptions.
https://github.com/bodbdigr/restea/blob/d0dbf7b/restea/resource.py#L201-L204

What is weird is the RestError-subclassed exceptions are being initialized passing the same catched instance of Error or ConfigurationError, which are actually not serializable, even for default formatter.

Do you think we can just use something like the following?

try:
    return self.fields.validate(payload_data)
except fields.FieldSet.Error as e:
    raise errors.BadRequestError(str(e))
except fields.FieldSet.ConfigurationError as e:
    raise errors.ServerError(str(e))

Thanks!

Hello,

In resource code, when applying decorators we are maybe using a wrong order, for instance:

class MyResource(Resource):
    decorators = [
        validate_authenticated_user,
        validate_permissions_on_user
    ]
    # ...

Anyone may think that the first ("validate_authenticated_user") will be called before to the second one ("validate_permissions"), but this is not actually how is working. May we can to apply decorators in reverse order?

Thanks!