interactions-py / astro Goto Github PK

Like the URL button in the button example, it is linked with the old docs, but they don't exist any more

/search and /paginator dinteractions-paginator don't work.
The only way that I found causing this issue while testing the code myself was with dinteractions-Paginator library version 1.1.12 or lower.
Please use pip install -U dinteractions-Paginator to fix this issue.

TL;DR: you forgot to update dinteractions-Paginator

Hey, I am a bit new to this and I made slash commands and every of my commands seems to work out perfectly fine except for the one that has no args, When I use my commands, it is like this

and when I try to enter:

and if I try to put random stuff in the kwargs

it says the kwargs thing is required but my command literally has no options in the @slash.slash thing and my actual command has only this:

async def <command name>(ctx: SlashCommand):

I don't know what to do but the issue is probably my fault as I said I am new to this

I think this makes us a little too pretentious now, we should probably word it better to say "we're using the go-to interactions based python library" or something along those lines.

The rewrite has been on hold until the paginator extension was made official. As of the time of this writing, the extension has been officially accepted and added to the organisation. Work will be made soon to reflect this by either me or anyone willing to contribute.

Currently, the get_roles endpoint provided by the API only return back the ID and no role object. A stopgap solution would be aggressively producing a temporary cache within the command by cross mapping the user's role IDs to the guild, but this is extremely inefficient and could quickly read to rate limitation. A more viable approach is letting the core library handle this in a sane manner when the cache is refactored.

Should we move from datetime.datetime to naff.Timestamp so we can access more of the information, and avoid having to manually convert to a timestamp object in some of our command responses? Considering message formatting for this one specifically

Since we're in the process of migrating the NAFF code base over to interactions.py, I expect us to have nearly, if not exactly the same amount of integral support of NAFF code. With a bot rewrite to the other library, we should be able to mitigate large changes later on in the long run.