interactions-py · EepyElvyra · Oct 6, 2022 · Aug 11, 2022 · Aug 14, 2022 · Aug 17, 2022
diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml
@@ -1,4 +1,4 @@
 # These are supported funding model platforms
 
-github: [goverfl0w]
+github: [i0bs]
 open_collective: interactions-py
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -4,12 +4,20 @@ This pull request is about (X), which does (Y).
 
 ## Checklist
 
-- [ ] I've ran `pre-commit` to format and lint the change(s) made.
-- [ ] I've checked to make sure the change(s) work on `3.8.6` and higher.
-- [ ] This fixes/solves an [Issue](https://github.com/goverfl0w/discord-interactions/issues) (If existent):.
-  - resolves #
-- I've made this pull request for/as: (check all that apply)
-  - [ ] Documentation
-  - [ ] Breaking change
-  - [ ] New feature/enhancement
-  - [ ] Bugfix
+- [ ] The ``pre-commit`` code linter has been run over all edited files to ensure the code is linted.
+- [ ] I've ensured the change(s) work on `3.8.6` and higher.
+
+
+I've made this pull request: (check all that apply)
+  - [ ] For the documentation
+  - [ ] To add a new feature
+  - [ ] As a general enhancement
+  - [ ] As a refactor of the library/the library's code
+  - [ ] To fix an existing bug
+  - [ ] To resolve #ISSUENUMBER
+
+
+This is:
+  - [ ] A breaking change
+
+  <!--- Expand this when more comes up--->
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
@@ -29,7 +29,7 @@ repos:
     - id: check-merge-conflict
       name: Merge Conflicts
   - repo: https://github.com/psf/black
-    rev: 22.6.0
+    rev: 22.8.0
     hooks:
     - id: black
       name: Black Formatting

diff --git a/docs/api.models.emoji.rst b/docs/api.models.emoji.rst
@@ -0,0 +1,7 @@
+.. currentmodule:: interactions
+
+Emoji Models
+================
+
+.. automodule:: interactions.api.models.emoji
+    :members:
diff --git a/docs/api.models.rst b/docs/api.models.rst
@@ -8,6 +8,7 @@ Model Objects
 
     api.models.audit_log.rst
     api.models.channel.rst
+    api.models.emoji.rst
     api.models.guild.rst
     api.models.gw.rst
     api.models.flags.rst

diff --git a/docs/api.rst b/docs/api.rst
@@ -20,7 +20,7 @@ Interactions
 
     ext.rst
     context.rst
-    get.rst
+    utils.rst
 
 .. toctree::
     :maxdepth: 2

diff --git a/docs/conf.py b/docs/conf.py
@@ -37,6 +37,7 @@
 
 # descriptions of the relevant function/method.
 autodoc_typehints = "description"
+autodoc_typehints_description_target = "documented_params"
 
 extensions = [
     "sphinx.ext.autodoc",

diff --git a/docs/events.rst b/docs/events.rst
@@ -66,9 +66,10 @@ Event: ``raw_socket_create``
 This event fires on any event sent by Discord, including ``Typing Start``  and ``Voice State Update``.
 ``Hello``, ``Resumed``, ``Reconnect`` and ``Invalid Session`` still will not be dispatched.
 
-The function handling the event should take in one argument, the type of this argument is a ``dict``.
+A function handling an event should take two arguments,
+the first argument is the name of the event, the second is the data of that event with type ``dict``.
 
-The value of the argument will be the *raw* data sent from Discord, so it is not recommended to use that event
+The value of the second argument will be the *raw* data sent from Discord, so it is not recommended to use that event
 as long as you don't absolutely need it.
 
 

diff --git a/docs/faq.rst b/docs/faq.rst
@@ -154,21 +154,22 @@ A list of all official extensions can be found `on our github page`_
 
 Those are (at the moment):
 
-- A `voice client`_ - which is still WIP, but it is able to listen for the ``VOICE_STATE_UPDATE`` event.
-- An `autosharder`_ for automatic sharding
+- `voice client`_ - which is still WIP, but it is able to listen for the ``VOICE_STATE_UPDATE`` event.
+- `autosharder`_ for automatic sharding
 - `wait_for`_ allows listening and waiting for a specific event or a component inside a function
 - `files`_ for file sending with ctx
 - `Molter`_ for message commands
 - `enhanced`_ which enhances the DX in general
-- A `paginator`_ for paginating embeds on messages using components
-- `persistence`_ - for storing data inside your custom IDs (as an alternative to ``wait_for``)
+- `paginator`_ for paginating embeds on messages using components
+- `persistence`_ for storing data inside your custom IDs (as an alternative to ``wait_for``)
+- `lavalink`_ for voice sending and listening ``VOICE_STATE_UPDATE`` event
+- `fastapi`_ for building own API
 - And a `boilerplate`_
 
 Below are a few unofficial exts (for the time being) which implement some functionality similar to what d.py had:
 
 - `checks and cooldowns`_
 - `tasks`_
-- `get`_ for getting objects from the discord API (will be implemented into the core library at a later time)
 
 Usage examples can usually be found at the linked page
 
@@ -318,4 +319,5 @@ Please join our `Discord Server`_ for any further support regarding our library
 .. _persistence: https://github.com/interactions-py/persistence
 .. _Molter: https://github.com/interactions-py/molter
 .. _boilerplate: https://github.com/interactions-py/boilerplate
-.. _get: https://github.com/EdVraz/interactions-get
+.. _lavalink: https://github.com/interactions-py/interactions-lavalink
+.. _fastapi: https://github.com/interactions-py/interactions-fastapi
diff --git a/docs/get.rst b/docs/get.rst
diff --git a/docs/index.rst b/docs/index.rst
@@ -8,7 +8,7 @@ Ever since December 2019, this open-source project has become the culmination of
 - Looking for a compatible library that implements all interactions?
 - Itching to get your hands on slash commands, but in a simple manner?
 
-Look no more! The goal of this library is to make all three of these questions go from possibilites to trivial matters.
+Look no more! The goal of this library is to make all three of these questions go from possibilities to trivial matters.
 
 What can we do?
 ***************
@@ -63,10 +63,10 @@ This open-source project utilizes the following workflows for development:
 #. **pre-commit** ``2.20.0``: the architecture uses this before every commit to format and check for severity/QOL-breaking changes.
 
    #. **black** ``22.6.0``
-   #. **flake8** ``4.0.1``
+   #. **flake8** ``5.0.4``
    #. **isort** ``5.10.1``
 
-#. **Sphinx** ``4.4.0``: all of our documentation is powered off of autogenerated documentation of the Sphinx engine.
+#. **Sphinx** ``5.1.1``: all of our documentation is powered off of autogenerated documentation of the Sphinx engine.
 #. **Conventional 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.
 
 When can I start?

diff --git a/docs/locale/de/LC_MESSAGES/api.dispatch.po b/docs/locale/de/LC_MESSAGES/api.dispatch.po
@@ -9,14 +9,14 @@ msgid ""
 msgstr ""
 "Project-Id-Version: interactions.py 4.3\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-07-17 16:00-0400\n"
+"POT-Creation-Date: 2022-09-26 12:28-0400\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <[email protected]>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.9.1\n"
+"Generated-By: Babel 2.10.3\n"
 
 #: ../../api.dispatch.rst:4
 msgid "Dispatching"
@@ -38,12 +38,6 @@ msgstr ""
 msgid "A list of events being dispatched."
 msgstr ""
 
-#: interactions.api.dispatch.Listener
-#: interactions.api.dispatch.Listener.dispatch
-#: interactions.api.dispatch.Listener.register of
-msgid "Return type"
-msgstr ""
-
 #: interactions.api.dispatch.Listener.dispatch:1 of
 msgid "Dispatches an event given out by the gateway."
 msgstr ""
@@ -83,3 +77,6 @@ msgstr ""
 #: interactions.api.dispatch.Listener.register:9 of
 msgid "The name to associate the coroutine with. Defaults to None."
 msgstr ""
+
+#~ msgid "Return type"
+#~ msgstr ""