Austin Keener

Lets go with the actual class (TextChannel) instead of the type (TEXT). The type gets weird for threads and the class is more explicit and understood by users. Going with...

I feel like we need to define a consistent format for these `toString` implementations. right now they are kinda.. all over the place. We need to define: - Name -...

Honestly, the strings start getting longer than what I'd like to see at that point. I'm not quite sure what the answer here is yet.

# Snowflakes - Current Implementations: - `"User(" + getId() + ')';` - `"Guild:" + getName() + '(' + id + ')';` - `"Member:" + getEffectiveName() + '[' + getUser() +...

## The Rest - I've not edited any of these yet. I pulled them straight from the code in the PR. Just pasting in one place to simplify visualizing them...

Bump. Considering start a review here soon but unclear on the activity in this PR. Is this orphaned?

Bump. Why is this in the freezer? Is this effected by the weirdness introduced by Public Instances of StageChannels?

I personally moved over to using [query-string](https://github.com/sindresorhus/query-string) to address this problem. You can achieve the `repeat` mode via query-string's `bracket` ```js const queryString = require('query-string'); queryString.parse('foo[]=1&foo[]=2&foo[]=3', {arrayFormat: 'bracket'}); //=> {foo:...

> All markdown items are displaying incorrectly (**bold**, _italic_, `code`, [hyperlinks](#), etc) This was addressed a long time ago (Stale issue, sorry about that!) > Markdown not properly rendering in...

I like the concept of `docs.jda.wiki` Is the only thing holding this back a merge and setting up the settings + domain? Also, what happens to docs for other versions,...