Making this library unique in a sense that we only do this seemed reasonable and within our margin of standards at the time. The goal of this library is to solely implement support and integrate the use of interactions from the Discord API. Forking discord.py and building off of it does not change anything from our issue of avoiding this. The original purpose of this library was to act as an extension of discord.py, but due to the issue of constantly having to monkeypatch solutions into their codebase to keep our library working introduced extreme technical debt. There are/will be numerous forks out there for discord.py, and because of that, we cannot safely guarantee our ability to help users out who may be using their own form of modified code. The long answer is a list of numerous reasons as to why this decision was made: This is the official statement from the library developer regarding this: Are you going to/will/consider fork(ing) discord.py? ¶ Was made before Danny posted his gist on GitHub about ceasing development of discord.py. The decision to become a standalone library that is now an API wrapper for the Discord API discord.py is dead! Will this library die too? ¶ For anyĬomments, feedback or concerns please consider joining our serverĪnd bringing it up in our support channels. You must be willing to change/adhere to reviews from participants where necessary.This page is maintained by the Helpers of the Discord server,Īnd developers at their discretion. colour for color)Ī request has to be approved by at least one developer. We do not accept abstraction-based requests. We also have some extra ground rules about making any specific contributions involving:
Sphinx 4.1.2: all of our documentation is powered off of autogenerated documentation of the Sphinx engine.Ĭolorama 0.4.4: our internal logger uses a customized coloring formatter to make looking for specific conditions easier when running tests.Ĭonventional Commits 1.0.0: every commit that we make to our branches use the official specification of CC 1.0.0 to make git graphs easier when improving and refining communication between code reviews, Pull Requests and commits.
Pre-commit 2.16.0: the architecture uses this before every commit to format and check for severity/QOL-breaking changes. This open-source project utilizes the following workflows for development: This open-source project also enforces the MIT License. Please read up on our contribution requirements for the project. While we certainly offer a lot of benefits, we unfortunately have our own downsides: Some more unique features that are exclusive to our interactions include:Įvent-triggered callbacks: whether a component, application command or interaction response, you’ll never need to worry about bridging responses.ĭual-way decorator logic: a decorator can act as both a constructor for an interaction, as well as a callback.ĪPI-strict naming: no more confusion with the naming approach of many libraries we follow the naming style of interactions from the officially curated Discord Developers documentation.Įxtensive framework structure: ( pending in 4.1.0) build your own tools and technologies for our library to develop and integrate community creations. Simplified data models: every object presented is accessible as either a raw dictionary/ application/json or list of recursive attributes. On-demand cache: every HTTP request and Gateway event made is cached when needed, so you never have to save information yourself. Sane rate limiting: our HTTP client implements pre-emptive rate limit avoidance, so your bot is guaranteed to never hit HTTP 429. The base features of our library, built with our API include:ĭynamic object data generation: all event data dispatched from the Gateway is dynamically transformed and generated into two-way serializable JSON objects. Our library-inside and out, offers numerous benefits and presents itself as a worthy module in your bot’s dependencies: Look no more! The goal of this library is to make all three of these questions go from possibilites to trivial matters. Itching to get your hands on slash commands, but in a simple manner? Looking for a compatible library that implements all interactions? Tired of using numerous module dependencies for slash commands and buttons? Ever since December 2019, this open-source project has become the culmination of dedication and research towards figuring out the best way to bring interactions from Discord to you: we are an easy, simple, scalable and modular library for Discord interactions.