Fix params allowed_updates on Telegram bot polling whenever it's an array #1269
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alfanzain
force-pushed
the
feat/stringify-allowed-updates-on-get-updates
branch
2 times, most recently
from
e251886 to
e4bb415
Compare
alfanzain
force-pushed
the
feat/stringify-allowed-updates-on-get-updates
branch
from
e4bb415 to
bdfcb68
Compare
alfanzain
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
masternpm run docDescription
The bot was not receiving updates for
message_reactionevents, even thoughallowed_updateswas specified in the polling config.Turns out, the
allowed_updatesparameter was not being correctly passed to the getUpdates call if it is an array. It needs to be JSON-stringified.This PR fixes the polling configuration to ensure that
allowed_updatesis properly passed as an array to the getUpdates method.References