Interaction Subclasses

[spifory]

Summary

There should be subclasses for Interaction depending on what the interaction is for.

What is the feature request for?

The core library

The Problem

I feel that there should be subclasses for Interaction since it would help provide the relevant attributes for certain situations. An example would be how <Interaction>.message should not work for modals (I think).

The Ideal Solution

Creating subclasses for Interaction in the library, like:

class Interaction:
    ...

class ModalInteraction(Interaction):
    ...

class ApplicationCommandInteraction(Interaction):
    ...

The Current Solution

No response

Additional Context

Disnake does do something like this, for reference.

[Gangsta-Muffin]

I will make an attempt at coding these items in the near future :)

~ Gangsta Muffin#5537