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
REST: should process_post flow include content_types_accepted? #356
Comments
This change might have to break stuff for rest handlers that conditionally return true from |
Yeah that's planned. |
I have a PR/patch for this if your interested check it out. |
Hey @BFrog I was hoping I could see with you for these PRs at some point. I'm sick right now so not exactly in the mood for it but perhaps next week? |
Sure that sounds good |
#296 would be a great improvement! Have to fork and cherry pick it. Can't wait to see it in vanilla cowboy. |
@BFrog I need a few changes to the existing PRs, and if you already have done POST can you open a PR for it too? Thanks. |
Patches welcome. |
Done in 5a171d0. Please open new tickets if there's issues. Thanks! |
I think
process_post
should happen after the appropriate content_types_accepted callback has been called. In 0.6.1 it seems thatcontent_types_accepted
is ignored whenpost_is_create
returns false and it doesn't seem like this changed up to master.The point of this change is that even when I'm doing a "process sort of" POST, I still want to do different decoding given
application/json
orapplication/x-www-form-urlencoded
. I can either do my processing in my provided callback or set the data in my state and do the processing inprocess_post
as per the current API.Am I missing something or does this sound sensible enough for a pull request?
The text was updated successfully, but these errors were encountered: