Description
It would be really handy for me to have stateless interactions.
In this case, stateless meaning; if the application restarts, the interaction can still be executed.
Use case scenario 1:
A permanent embed with buttons, that will continue to work through restarts.
Use case scenario 2:
I could no longer use await interactivity.ButtonAsync or interactivity.ModelAsync and break interactions, or have the user restart the interaction if the timeout exceeds.
@OoLunar has already informed me this will not be apart of #2153
Specify the libraries you want this feature request to affect
DSharpPlus.Interactivity
Other considerations
I would take a guess and say something along the lines of using attributes to match customIds, with the ability to be somewhat dynamic with maybe Regex, for example mybutton1-5ecf7a39-79fb-4166-b851-f05f0bf3a325, where D#+ would search for mybutton1 in user code and provide 5ecf7a39-79fb-4166-b851-f05f0bf3a325 as a parameter.
Reactions are currently unavailable
Description
It would be really handy for me to have stateless interactions.
In this case, stateless meaning; if the application restarts, the interaction can still be executed.
Use case scenario 1:
A permanent embed with buttons, that will continue to work through restarts.
Use case scenario 2:
I could no longer use await interactivity.ButtonAsync or interactivity.ModelAsync and break interactions, or have the user restart the interaction if the timeout exceeds.
@OoLunar has already informed me this will not be apart of #2153
Specify the libraries you want this feature request to affect
DSharpPlus.Interactivity
Other considerations
I would take a guess and say something along the lines of using attributes to match customIds, with the ability to be somewhat dynamic with maybe Regex, for example mybutton1-5ecf7a39-79fb-4166-b851-f05f0bf3a325, where D#+ would search for mybutton1 in user code and provide 5ecf7a39-79fb-4166-b851-f05f0bf3a325 as a parameter.