Split Rest Classes & Normal Classes #1124
Description
Due to the way the getREST functions work, they cannot support a lot of the normal functions. I think they should be split into multiple classes, at least, as far as typings go. Having different types would avoid random issues where guild members, shards, etc are missing when they usually wouldn't be. Currently, the only way to know these are missing is common sense (which isn't common, and things can get overlooked sometimes), or actually having the errors happen. For instance, running removeRole on a rest guild member will produce something like this:
[Eris code] [my code]
Finding ways to still run these functions, or separating them from shards somehow, or just flat out removing them, if it comes to that, can help with a lot of confusion around why certain things don't work on REST objects.