We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some routes, as mentioned in the documentation, don't require automatic body parsing at all and break if it occurs because the body is used due to side effects introduced by plugins (i.e. how elysia works)
Allow parse: false option in the route's configuration, or reconsider parsing for plugins that don't access the body but Context
parse: false
Context
app.post("/", betterAuthView, { parse: false, });
Allowing something like this should also improve performance
I tried this, but it is inconsistent with aot: false, in some cases and bad UX:
aot: false
app.post("/", betterAuthView, { parse: () => 0, });
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What is the problem this feature would solve?
Some routes, as mentioned in the documentation, don't require automatic body parsing at all and break if it occurs because the body is used due to side effects introduced by plugins (i.e. how elysia works)
What is the feature you are proposing to solve the problem?
Allow
parse: false
option in the route's configuration, or reconsider parsing for plugins that don't access the body butContext
Allowing something like this should also improve performance
What alternatives have you considered?
I tried this, but it is inconsistent with
aot: false
, in some cases and bad UX:The text was updated successfully, but these errors were encountered: