Replies: 1 comment 3 replies
-
This caching behaviour is from the client itself, it's not related to the library in any way. It's a long standing upstream issue: discord/discord-api-docs#4804 As far as I know there's no workaround. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I didn't find proper information on this, but I have a case with a command that take 2 arguments:
name
anddate
.Both parameters have autocomplete, however
date
choices is relative to selectedname
. So in date autocomplete I getinteraction.namespace.name
argument and based on it filter available dates for that name.The problem goes with caching. For example I type command
/command [name: A] [date: 2]
and get some dates choices from that name that contain2
in it, like2024.07.06
However if in that state I delete with backspace date variable and change name to
B
, then type[date: 2]
again, the choices I get before would be restored and bot would not get hit with an autocomplete function call (I checked that withprint
).So now I have obsolete values that somehow cached and wont update to new proper ones. Even if I delete whole command and re-type again it wont do that. Only until I restart bot. How to prevent this caching behavior?
Beta Was this translation helpful? Give feedback.
All reactions