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

docs: update api.md for setWebHook (fix #1083) #1084

Merged
merged 1 commit into from
Aug 22, 2023

Conversation

rznzippy
Copy link
Contributor

  • All tests pass
  • I have run npm run doc

Description

Add missing setWebhook secret_token parameter to the documentation

References

@XieJiSS
Copy link

XieJiSS commented May 11, 2023

Thanks for the PR! I'd like to suggest to clarify in the doc that the user needs to verify the X-Telegram-Bot-Api-Secret-Token manually because there's currently no such verification logic implemented in node-telegram-bot-api.

Or maybe we can implement a verification logic inside the library so that the user won't need to bother with getting and checking headers for every webhook request.

Copy link
Collaborator

@kamikazechaser kamikazechaser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

You can also add some simple check here https://github.com/yagop/node-telegram-bot-api/blob/master/examples/webhook/express.js to show how to use it (along with any inline documentation).

@JamolMeyliyev
Copy link

secret-bot-token what?

@danielperez9430 danielperez9430 merged commit dfe24a4 into yagop:master Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add missing setWebhook secret_token parameter to the documentation
5 participants