Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postprocessors don't get fired, when item is not found #417

Open
madvas opened this issue Mar 5, 2015 · 1 comment
Open

Postprocessors don't get fired, when item is not found #417

madvas opened this issue Mar 5, 2015 · 1 comment

Comments

@madvas
Copy link

madvas commented Mar 5, 2015

Is there a specific reason why postprocessors don't get fired when item is not found? I think that's the ideal place where to implement 'GET or INSERT' feature.

I've got this code:

postprocessors={
    'GET_SINGLE': [get_or_insert_item],
})
@jfinkels
Copy link
Owner

jfinkels commented May 3, 2016

It is currently considered an error response (404 Not Found), and we aren't applying postprocessors on any error responses, only on non-error responses. It doesn't necessarily have to be that way, that's just the way it exists now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants