Data attribute

[TheUntraceable]

For most of the classes we have, we depend on a data argument, we also include a client arg for some objects. We should add a data attribute that will represent the data that we took in so that people can modify it to their needs if we don't make an update and there's a new feature. Shouldn't take too long to add but gonna be a little tedious to add.

[TheUntraceable]

I'll do this before the major release of 1.0 because it'll need me to go to every class and show the data attribute.

[nav-github01001]

@TheUntraceable it is done

[TheUntraceable]

What

[nav-github01001]

Done it rt

[TheUntraceable]

Not really

[EmmmaTech]

We should add a data attribute that will represent the data that we took in so that people can modify it to their needs if we don't make an update and there's a new feature. Shouldn't take too long to add but gonna be a little tedious to add.

This doesn't make sense. With objects returned from the Discord API, they shouldn't be modified locally because those changes won't be in sync with the Discord API. In turn, this will cause confusion.

[TheUntraceable]

The point of this is so that even if I stop maintaining the library, you should still be able to use it.

New attribute? It's in the .data