Closed svenwiltink closed 1 year ago
Well first things first, it's time to update the API version to something non-deprecated - especially when dealing with these channel types.
Though it also doesn't return the data in v10
whoops. Edited the original post to reflect the api version I actually tried. Copied the wrong version from my terminal after trying a bunch of versions
Hey, is there a workaround for this or something?
Hey, is there a workaround for this or something?
Doing a request per thread to get its applied tags
How do I do this?
And is this temporary or is this the new way to get the tags?
How do I do this?
With this
And is this temporary or is this the new way to get the tags?
Until an employee responds, we don't know. Considering there's a synced
label to the issue they are/will be looking into it.
That is what we've done as well: https://github.com/discord-gophers/forumcleaner/blob/50f87306d28b6c8c99c91c90e11071e65ad42572/main.go#L165-L170
This is fixed now
Description
The active threads resource used to list applied_tags because it returns a list of channel objects. Instead of performing a single call to list all active threads with a certain tag applied we now have to perform N requests, where N is the amount of active threads.
Steps to Reproduce
list active threads https://discord.com/api/guilds/118456055842734083/threads/active
Expected Behavior
Expecting the body to contain applied_tags
Current Behavior
body does not contain applied tags
Screenshots/Videos
Client and System Information
Just using curl