-
Notifications
You must be signed in to change notification settings - Fork 3
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
70 automatically signin user who creates signin #77
70 automatically signin user who creates signin #77
Conversation
Allow Kudos for Multiple Users
I will look closer when I get home. But looks like you did not change existing interaction response, so it will |
Yeah, I am aware of that. Was going to communicate with you about that, just confused about it. |
commands/slash/signin.go
Outdated
err = s.InteractionRespond(i.Interaction, &discordgo.InteractionResponse{ | ||
Type: discordgo.InteractionResponseChannelMessageWithSource, | ||
Data: &discordgo.InteractionResponseData{ | ||
Content: signinMessage(i.Member.User.ID, entSigninType, span.Context()), | ||
Flags: discordgo.MessageFlagsEphemeral, | ||
}, | ||
}) | ||
if err != nil { | ||
logging.Error(s, err.Error(), i.Member.User, span, logrus.Fields{"error": err}) | ||
return | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Message is sent to command user here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These both use the same interaction; best way to do this is just combine this into the later one
change user to be the person executing command, should be something like i.Member.User.ID
change span context to match execution block (use span instead of span_signinSlug)