[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
📚 Description
I have fixed the url used for Discord oath2 authorization. It required the removal of the /api part in the route in accordance with Discords OAuth2 documentation (read here: https://discord.com/developers/docs/topics/oauth2).
Furthermore, I added a parameter to the request called "integration_type" and I set the value to 1. Though the Discord documentation states that it is unnecessary unless a specific scope is being called, I kept receiving an error that said "Installation type not supported for this application". I solved it by adding the integration type and setting it to user install.
📝 Checklist
I have not linked an issue or discussion, as I did not see one. I also do not believe this change will require any change to the documentation.
RomainLanz
commented
5 months ago
🔗 Linked issue
❓ Type of change
📚 Description
I have fixed the url used for Discord oath2 authorization. It required the removal of the
/apipart in the route in accordance with Discords OAuth2 documentation (read here: https://discord.com/developers/docs/topics/oauth2).Furthermore, I added a parameter to the request called "integration_type" and I set the value to 1. Though the Discord documentation states that it is unnecessary unless a specific scope is being called, I kept receiving an error that said "Installation type not supported for this application". I solved it by adding the integration type and setting it to user install.
📝 Checklist
I have not linked an issue or discussion, as I did not see one. I also do not believe this change will require any change to the documentation.