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

Transition payload hash option names to hmac #461

Merged
merged 1 commit into from
Sep 28, 2020

Conversation

moorereason
Copy link
Collaborator

The payload-hash-* options are imprecisely named. Clarify their function
as HMAC validations by renaming them. The existing options will continue
to work but are deprecated. Log a warning if the old options are used.

All tests, examples, and documentation are updated.

Fixes #289

@moorereason moorereason added this to the 2.8.0 milestone Sep 25, 2020
@moorereason moorereason added this to In progress in Development Sep 25, 2020
@adnanh
Copy link
Owner

adnanh commented Sep 27, 2020

Needs conflict resolution now, otherwise, looking forward to merge it in :-)

The payload-hash-* options are imprecisely named. Clarify their function
as HMAC validations by renaming them. The existing options will continue
to work but are deprecated.  Log a warning if the old options are used.

All tests, examples, and documentation are updated.

Fixes adnanh#289
@moorereason
Copy link
Collaborator Author

Rebased.

@adnanh adnanh merged commit 0f4bbfa into adnanh:development Sep 28, 2020
@moorereason moorereason moved this from In progress to Done in Development Sep 28, 2020
benjaoming added a commit to benjaoming/webhook that referenced this pull request Apr 25, 2021
adnanh#461 changed option name and in adnanh#528 (comment), @moorereason suggests to look at old tags of example documentation. This would mean that users have to read through random old documentation to discover why their packaged version doesn't work . Suggesting that clarity in the examples is preferable.

Recall that renaming this doesn't give the user some easy exception. It just mean that the trigger isn't satisfied, so there are A LOT of options for debugging.

(which takes a lot of time to do, so that's why this information is important)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

2 participants