Create a signature validation function that is not tied to the request

[danerwilliams]

Description

There is currently a PR #1359 and issue #1358 to expose common utilities, including a signature validation function .

This issue suggests creation of a signature validation function that is less tightly coupled to the request than the function that will be exposed in #1359.

With the existing function, it becomes difficult to use with nest.js or other frameworks that modify incoming requests. Ideally this function would take the request body + headers, and signing secret. It would then perform the validation and if successful return the webhook's event object.

What type of issue is this? (place an x in one of the [ ])

• bug
• enhancement (feature request)
• question
• documentation related
• example code related
• testing related
• discussion

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

[seratch]

Hi @danerwilliams, thanks for the great suggestion! We will consider having an additional utility for your use case in the next release.