You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
content=f"Responded! The content of the message targeted: {ctx.target_message.content}",
369
370
hidden=True
370
371
)
371
372
372
373
The `@slash.context_menu` decorator takes in the context type as given (to either appear when you right-click on a user or when you right-click on a message) as well
373
374
as the name of the command, and any guild IDs if given if you would like to make it applicable to only a guild. **We only accept connected names** for the time being,
374
375
although context menus will have the ability to have spaces in their name in the future when development further progresses.
375
376
377
+
You are able to also use the `@cog_ext.cog_context_menu` path which will require an import from `cog_ext.py` respectively, however, it is worth nothing that
378
+
the `target` kwarg for the decorator **must** be brought to the very end.
379
+
380
+
Can I use components with context menus?
381
+
----------------------------------------
382
+
Of course! However, you will need to add in some additional code in order for both of the separate contexts to work seamlessly. Below is the given code of what will need
383
+
to be changed:
384
+
385
+
.. code-block :: python
386
+
387
+
from discord_slash.context import ComponentContext, MenuContext
The decision has been made that this will not be implemented because of two reasons: context menus currently have no ability to hold any options or choices, so listening
0 commit comments