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.
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
Slash commands #856
Slash commands #856
Changes from 17 commits
d7f3449
356455e
d703a29
854e96d
4aeca90
af426c1
c1d8bff
3f37ec0
5b23e34
1c8faf9
9c6bf00
f554a2f
b76c150
f4cfc0f
2028ce6
75a2e2d
f5375a0
00e6233
a1b4fed
8718e2d
4b3f141
3bc1011
1f39a0c
4d4cfa2
01ab497
372eb32
f6396f4
ae60d65
da4ca39
2274e22
4a31b48
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Is changing the value of EndpointApplications to mean another thing really a good idea?
Note to others: The previous EndpointApplications is now known as EndpointOAuth2Applications.
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.
I needed to change it. Because EndpointApplications now doesn't belong to OAuth2. It belongs to applications and their commands.
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.
Yeah but this might cause a problem on the off chance someone was relying on EndpointApplications to be with OAuth2.
It IS an exported variable after all.
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.
Reasonable question: how I need to name it then, tell me. Applications and OAuth2 applications isn't the same thing now. And also, why are everyone tries to save backward compatibility even when WE JUST CAN'T???? Because API is changed and we need to change something, not sit on the same place as we was before.
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.
Adding things to an API doesn't break compatibility, but removing and modifying things can eg:
For example, something as innocuous as:
This will now cause a compiler error when updating with this PR.
It's our job as library maintainers to minimize these scenarios, even when they cause the code to not be exactly what we would like in a perfect world.
Ps. It feels like you're getting upset by this code review, please remember that these comments aren't a criticism of you as a person, just they reflect the combined experience of a number of people also trying to do a good job - we're working together to make this the best PR possible!
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.
Of course I'm upset.
I can't save
EndpointApplication
here, because Discord API changed it and it no longer "OAuth2" applications. Or at least, I'm waiting for suggestions what name I should pick for new ones if I will return EndpointApplications and other OAuth2 stuff back to original.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.
Code review isn't a criticism of you as a person, I'm sorry you're feeling upset, but that is not the intention. As the maintainers of the library, we have a responsibility to our users, and we are essentially signing up to being the maintainers of this code in the future.
My apologies for speaking without fully getting context on this.
I've done some searching, it seems like there is no code on Github or Google currently using EndpointApplication, I'm happy with renaming this to EndpointOauth2Application, but I would like us to add a warning in the release notes.
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.
Yeah, that's right, I appreciate that decision. Well, actually, we can try to create another name for current applications endpoint, but... that would be really hard to rename in future. So, yeah, you're right, warning in release notes is enough for this. Btw, when will be release?
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.
Just want to note that many of the larger discord bots tend to be private codebases, and those may be more likely to use oauth flows in e.g. web dashboards or what not, where these variables may be used @iopred
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.