Skip to content
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

Request compatibility subclass for gateway #11

Open
Bluenix2 opened this issue Apr 9, 2022 · 0 comments
Open

Request compatibility subclass for gateway #11

Bluenix2 opened this issue Apr 9, 2022 · 0 comments
Labels
feature New addition to the library good first issue Good for newcomers minor Deprecate, remove, or add a feature wumpy-bot

Comments

@Bluenix2
Copy link
Collaborator

Bluenix2 commented Apr 9, 2022

Summary

Although not recommended, there are those who wish to handle interactions over the gateway. This is afterall supported by the API, so it should be supported by the library. To do this, a Request subclass should be created that uses the Create Interaction Response endpoint.

Description

wumpy-interactions itself should only contain code for the original interactions over HTTP, therefore this subclass should be placed in the higher-level wumpy-bot.

Because you can't respond to an interaction with an error code, if data isn't present when called, it should do nothing which causes the same Interaction failed response by Discord.

Take a look at the other Request subclasses and the InteractionRequester for how to connect the two.

@Bluenix2 Bluenix2 added good first issue Good for newcomers feature New addition to the library minor Deprecate, remove, or add a feature labels Apr 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New addition to the library good first issue Good for newcomers minor Deprecate, remove, or add a feature wumpy-bot
Projects
Status: 📁 - Planning
Development

No branches or pull requests

1 participant