-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add thumbs up reaction #78
Conversation
jetersen
commented
Aug 10, 2022
•
edited
Loading
edited
- Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
- Ensure that the pull request title represents the desired changelog entry
- Please describe what you did
- Link to relevant issues in GitHub or Jira
- Link to relevant pull requests, esp. upstream and downstream changes
- Ensure you have provided tests - that demonstrates feature works or fixes the issue
app/router.js
Outdated
: await reportError(authToken, payload.issue.node_id, result.error); | ||
await (result.enabled | ||
? Promise.all([ | ||
addReaction(authToken, payload.issue.comment.node_id, "THUMBS_UP"), |
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.
Oh wait we are adding a comment for each commands recognized.
Perhaps we just do thumbs up whether it is enabled or not to show that we received the command.
? await command.run(authToken) | ||
: await reportError(authToken, payload.issue.node_id, result.error); | ||
try { | ||
await addReaction(authToken, payload.comment.node_id, "THUMBS_UP"); |
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.
you had an extra level of nesting here under issue which didn't exist.
Gave a nice excuse to add error handling though :)
Changed it to not error if reaction failed in #79 |