Jiralite
Jiralite
This is a breaking change, no? What happened?
~~Thoughts on replacing the logic of `role.memberCounts` with a cached version of this?~~ ~~We do the same elsewhere e.g. vanity data for a guild.~~ I meant `role.members`–not the same thing.
What about making the second parameter of all these methods an object that has a `raw` option (and `required`, of course) to return the payload from the API?
Yeah... from reading the feature request, using that method is not desired. Unless I'm reading it wrong.
I believe I can no longer reproduce. I'm guessing since the "hour" has passed, it has become fine now.
Hi @abalabahaha, any chance this could be looked at soon?
I think this may be related: https://github.com/discord/discord-api-docs/issues/6561#issuecomment-1839512039
> As of #11252 the error is actually different for hitting the ratelimit Specifically after #11253, this will throw, so point 2 in #11245 will no longer be relevant in...
Note: communication disabled checks are a duplicate of #9730. There is discussion in there on paths forward, but nothing has come of it (yet).
Announcement channels can be used in non-community guilds (simply turn community off). It probably still allows publishes. That is something to test.