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.

Sign up for GitHub

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

Jump to bottom

feat: enable custom content-type parsers #79

Open
javiergarea opened this issue Sep 9, 2024 · 0 comments
Open

feat: enable custom content-type parsers #79

javiergarea opened this issue Sep 9, 2024 · 0 comments

Comments

@javiergarea
Copy link
Member

Currently, only applicaton/json is supported as content-type for deserialization in the preprocess step. In case the content-type is absent or is not equal to application/json the body is passed as a binary to the callback function.

A nice solution would be to allow custom parsers (as MFAs or HOFs) per content-type in erf's configuration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
erf
Status: 📑 TODO
Milestone
No milestone
Development

No branches or pull requests
1 participant
@javiergarea