Interaction Handlers!!

Hello peeps!

I know, I know, allllll of you (myself included) are just basically begging me for application commands in Sapphire (and they're coming, don't you worry 😉), but we have to start slow. For now, I have some proper "documentation" on interaction handlers! 🎉

Are you ready to be HYPED?! (I hope.. please.. I'm trying my best here ;w;)

Have a read: https://vladfrangu.notion.site/Handling-Interactions-not-Application-Commands-in-Sapphire-92e307005b9f4e3b849663ea43c57701

I'll also turn this message in a thread, so leave alll your feedback, thoughts and whatnot in it! 🙏 🥺

This is what I kinda wished I had- separate verification versus running. This is awesome.

or the ability to have separate things :)

is the edit better?

👍

Also notion.so? God bless whoever made it

if this is your first time on notion

🚀 you're going to the moon

RIGHT

damn, very good guide

Thats something I forgot to write

LOL

Could you outline an example using both parse and run returning custom data?

I think this could be incredible to share data between the validation state and the running state, and seeing an example could help people understand the usage of this.

Added the section for what the fuck are these

Hope that helps

Technically, both examples in the parse section show how parse and run interact together

Ah, ok. I missed that entirely somehow. Thanks.

(I didn't see the type 👀)

Would this result in type completion, or would we need to type stuff ourselves?

(I will assume the latter)

@Vladdy could you do the guide on the other sapphire stuff? is that you do it very well

don’t make vlad do anything else. we’re just now getting all this out of the way. the guides will come in 10 years lol

Link to the docs.

What type? @24

It's true

What you place in this.some

eslint rule

you can have private constructors you know

ANYWAYS

hope it helps

ok all my questions are answered.

Maybe™️

ok so

we have it

1 down, 4 to go

4??

yeah I got one already

wait what

confused

thanos reference

AH

Also the answer is sadly no, you'll have to manually specify the type in the run function, just like you have to do in commands with the args class

I accept that responsibility.

Thank you.

looks interesting

I deadass wrote 992 words for this

Wow

well ok i'm the demand for nicer button handlers then

Yeah honestly, I know that they can mean different things, but I can't help my brain from wanting interactions over interaction-handlers (and also tasks over scheduled-tasks)

It just looks so much cleaner

In this case, interactions are what you receive, and you need a handler for it. I know it's a long name, you can blame the rest for it not being camelCase, but I doubt it'll change

Can we enforce the type of the result pass in this.some?

It's fun to type it in run but as long as this.some is not typed, the type in run has little usecase as this.some could still pass something very different

also @Vladdy I am working right now, I wouldn't dissapoint you not doing this while working

Even if I made it a generic on the class level it wouldn't help. This is why our event classes don't infer the types received in the run method when you set the event in the class generic. If we'd make the run method a class field..that might work but that's not something I'm gonna do

So it's up to the user to type their things right, and if they're using typescript that won't be hard

And js users just don't have to bother with this 😂

😂😂😂 up to you

HOWEVER

I might be able to make a utility in the namespace

@Y U G E Ni have a present for you

let me just document it in notion

I know

I read it

in #old-coding-den

And I love you for it

Added the changelog: https://www.notion.so/vladfrangu/Handling-Interactions-not-Application-Commands-in-Sapphire-92e307005b9f4e3b849663ea43c57701#68d96ce3554841cdb94a63da75a0793f
CC @Anger 🧶 since you're a TS nerd

You asked, I provided

Because I agree it's nice to have