Update docs and add migration

Author: quirky-bluejay

docs/faq.rst

@@ -109,7 +109,7 @@ Pretty much anything from the discord's commands extension doesn't work, also so
 .. warning::
    If you use something that might take a while, eg ``wait_for`` you'll run into two issues:
 
-   1. If you don't respond within 3 seconds (``ctx.respond()``) discord invalidates the interaction.
+   1. If you don't respond within 3 seconds (``ctx.defer()`` or `ctx.send(..)``) discord invalidates the interaction.
    2. The interaction only lasts for 15 minutes, so if you try and send something with the interaction (``ctx.send``) more than 15 mins after the command was ran it won't work.
 
    As an alternative you can use ``ctx.channel.send`` but this relies on the the bot being in the guild, and the bot having send perms in that channel.

docs/gettingstarted.rst

@@ -54,17 +54,12 @@ code as shown below:
   @slash.slash(name="test",
                description="This is just a test command, nothing more.")
   async def test(ctx):
-    await ctx.respond()
     await ctx.send(content="Hello World!")
     
 Now that we've gone over how Discord handles the declaration of slash commands
 through their Bot API, let's go over what some of the other things mean within
 the *logical* part of our code, the command function:
 
-- ``ctx.respond()``: This is a way for us to handle responses. In short, the API
-requires some way to "acknowledge" an interaction response that we want to send off.
-
-(An alias of this would be ``ctx.ack()``)
 
 Giving some options for variety.
 --------------------------------
@@ -163,7 +158,6 @@ Now, we can finally visualize this by coding an example of this being used in th
                  )
                ])
   async def test(ctx, optone: str):
-    await ctx.respond()
     await ctx.send(content=f"I got you, you said {optone}!")
     
 Additionally, we could also declare the type of our command's option through this method shown here:
@@ -233,7 +227,6 @@ a string or integer. Below is an implementation of this design in the Python cod
                  )
                ])
   async def test(ctx, optone: str):
-    await ctx.respond()
     await ctx.send(content=f"Wow, you actually chose {optone}? :(")
 
 .. _quickstart: https://discord-py-slash-command.readthedocs.io/en/latest/quickstart.html

docs/index.rst

@@ -26,7 +26,7 @@ discussion on GitHub!
 
    quickstart.rst
    gettingstarted.rst
-   migrate_to_109.rst
+   migration.rst
    discord_slash.rst
    events.rst
    discord_slash.utils.rst

docs/migrate_to_109.rst renamed to docs/migration.rst

@@ -1,3 +1,60 @@
+Migration
++++++++++
+This page contains instructions on how to migrate between versions with breaking changes.
+
+Migrate To V1.0.10
+==================
+Changes that you'll need to make in this version are mainly becuase of a new ui from discord, more info `here <https://github.com/discord/discord-api-docs/pull/2615>`_
+
+Responding / Deferring
+**********************
+
+In regards to :class:`SlashContext` the methods ``.respond`` and ``.ack`` have been removed, and ``.defer`` added. 
+Deferring a message will allow you to respond for up to 15 mins, but you'll have to defer within three seconds.
+When you defer the user will see a "this bot is thinking" message until you send a message, This message can be ephermical (hidden) or visible.
+``.defer`` has a ``hidden`` parameter, which will make the deferred message ephermical.
+
+We suggest deferring if you might take more than three seconds to respond, but if you will call ``.send`` before three seconds then don't.
+
+.. note::
+    You **must** respond with ``.send`` within 15 minutes of the command being invoked to avoid an "interaction failed" message, if you defer.
+    This is especially relevant for bots that had 'invisible' commands, where the invocation was not shown.
+    If you wish to have the invocation of the command not visible, send an ephermical success message, and then do what you used to.
+    It is no longer possible to "eat" the invocation.
+    ``ctx.channel.send`` does **not** count as responding.
+
+Example
+--------
+
+.. code-block:: python
+
+    # Before
+    @slash.slash(...)
+    async def command(ctx, ...):
+        await ctx.respond()
+        await ctx.send(...)
+    
+    # After 1
+    @slash.slash(...)
+    async def command(ctx, ...):
+        await ctx.send(...)
+
+    # After 2
+    @slash.slash(...)
+    async def command(ctx, ...):
+        await ctx.defer()
+        # Process that takes time
+        await ctx.send(...)
+
+    
+Sending hidden messages
+***********************
+The method ``.send_hidden`` on :class:`SlashContext` has been removed. Use ``.send(hidden = True, ..)`` instead.
+
+
+
+
+
 Migrate To 1.0.9
 ================
 

docs/quickstart.rst

@@ -52,7 +52,6 @@ slash commands just yet. We can do that by adding this code shown here:
 
     @slash.slash(name="ping", guild_ids=guild_ids)
     async def _ping(ctx): # Defines a new "context" (ctx) command called "ping."
-        await ctx.respond()
         await ctx.send(f"Pong! ({client.latency*1000}ms)")
 
 Let's compare some of the major code differences between the prior examples in order