View model for message components

[ghost]

Summary

As we discussed on Discord, the implementation of a View class, similar to how disnake handles them (examples can be found here)

Preferred Behaviour

With the ability to create a class for commonly used views such as pagination, confirmation etc. (example for confirmation here) it would reduce redundancy while also maintaining ease-of-use.

Suggestions

My suggestion would be a view argument in UserMessageCreateBuilder, so it could look like createMessage(view=Confirm) {...}. Granted, I do not know if that is within scope.

[gdude2002]

Interesting concept - I think this is probably a good way to go given how Kord's APIs work (and that I refuse to maintain a fork of it), though it definitely couldn't be part of createMessage - that's why the components builder doesn't do this already!