ref: replace "ctx.from.language_code" with a function to get the lang… #51
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: ABOCN/TelegramBot#51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "set_types"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
…uage code and fix ts implementation for "reply_to_message_id"
Great work! Thanks so much for your contribution, Giv, especially with how busy you are!
I made two quick comments for you to review, then I think it's good to go!
You might have forgot to go back to this
@ -3,2 +5,4 @@
const reply_to_message_id = replyToMessageId(ctx);
if (!userInput || (verifyNaN && isNaN(Number(userInput)))) {
ctx.reply(message, {
parse_mode: "Markdown",
Do we have any consensus on the
isNaN
? I'm not sure why it was used.Comment from code:
// not sure why isNaN is used here, but the input should be a number
@ -3,2 +5,4 @@
const reply_to_message_id = replyToMessageId(ctx);
if (!userInput || (verifyNaN && isNaN(Number(userInput)))) {
ctx.reply(message, {
parse_mode: "Markdown",
EDIT: it is not tho, never messed with verifyInput
The isNaN thing is my fault I think, but I don't really know why I put it there... See some diffs to confirm, please!
sadly this part is returning an error, I need to check why and what to do in this specific situation
also this part should be refactored imo
I'm going to close and merge this now to make it easier for me to fix some of these issues. @GiovaniFZ Can you start making branches in the
TelegramBot
repo so it's easier to make changes without making a PR to your repo?