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

Basic endpoint implementation #255

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

TAG-Epic
Copy link
Member

@TAG-Epic TAG-Epic commented Jul 13, 2023

This is not called webhook because of potential confusion between this and the channel webhooks.

This is for anything that receives HTTP requests originating from Discord's servers.

My structure for this is going to be to

  • Create a adapter per web-framework that sets up a app and HTTP paths, and passes the processed data from the request to the main class
  • A main class, unsure of a name that takes the data from the adapters and dispatches it and does logic stuff.

Unsure of how the different features like interactions and oauth are going to fit into this as there is quite a lot of features to cram into one class, however I don't know any better way to structure it.

TODO:

  • Make docs readable
  • Interactions
  • OAuth
  • Try to extend the compatible versions of the packages added
  • Tests for new Dispatcher feature
  • Tests for all endpoint stuff
  • Add example usages to the docs

This is not called webhook because of potential confusion between this
and the channel webhooks.

This is for anything that receives HTTP requests originating from
Discord's servers.

My structure for this is going to be to
- Create a adapter per web-framework that sets up a app and HTTP paths,
  and passes the processed data from the request to the main class
- A main class, unsure of a name that takes the data from the adapters
  and dispatches it and does logic stuff.

Unsure of how the different features like interactions and oauth are
going to fit into this as there is quite a lot of features to cram into
one class, however I don't know any better way to structure it.
@TAG-Epic TAG-Epic added the type/feature A feature addition label Jul 13, 2023
@TAG-Epic TAG-Epic marked this pull request as draft July 13, 2023 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature A feature addition
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant