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

Update info on how to process webhooks by disabling bodyParser #33909

Merged
merged 5 commits into from Feb 2, 2022

Conversation

amandeepmittal
Copy link
Contributor

@amandeepmittal amandeepmittal commented Feb 2, 2022

Explicitly mention disabling bodyParser when processing a webhook request. Uses the "webhook" keyword that becomes searchable in the docs for anyone running a search from the sidebar.

It addresses the issue here and this discussion.

Documentation / Examples

  • Make sure the linting passes by running yarn lint

amandeepmittal and others added 2 commits February 2, 2022 21:25
Co-authored-by: JJ Kasper <jj@jjsweb.site>
Co-authored-by: JJ Kasper <jj@jjsweb.site>
@kodiakhq kodiakhq bot merged commit ee2725f into vercel:canary Feb 2, 2022
@amandeepmittal amandeepmittal deleted the process-webhooks branch February 2, 2022 16:55
natew pushed a commit to natew/next.js that referenced this pull request Feb 16, 2022
…l#33909)

Explicitly mention disabling `bodyParser` when processing a webhook request. Uses the "webhook" keyword that becomes searchable in the docs for anyone running a search from the sidebar.

It addresses the issue [here](https://github.com/vercel/documentation/issues/71) and [this discussion](vercel/community#93).

## Documentation / Examples

- [x] Make sure the linting passes by running `yarn lint`
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
created-by: Next.js docs team PRs by the Next.js docs team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants