feat(channel): modify a thread, tags and all - #13
Merged
Merged
Conversation
A forum post's tags could be read off Channel::$applied_tags but never written: no builder carries the field, so there was no way to move a post from "voting" to "accepted" through the library. Every forum workflow turns on exactly that. A thread is not an ordinary channel. It has no topic, no permission overwrites and no parent to move it between, and it has archiving, locking and tags, which no other channel has. Passing one to a guild channel builder sends fields Discord rejects for a thread and offers none of the ones that apply, so this is its own builder rather than another trait bolted onto the existing ones. applied_tags replaces the whole set, since that is what Discord does with the field, and is reindexed on the way out: an array with gaps in it serialises to an object and the call comes back refused.
github-actions Bot
pushed a commit
that referenced
this pull request
Sep 2, 2026
## [1.3.0](v1.2.0...v1.3.0) (2026-09-02) ### Features * **channel:** modify a thread, tags and all ([#13](#13)) ([999e2ff](999e2ff))
|
🎉 This PR is included in version 1.3.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A forum post's tags can be read off
Channel::$applied_tagsbut never written: no builder carries the field, so there is no way to move a post from "voting" to "accepted" through the library. Every forum workflow turns on exactly that.Why its own builder rather than a trait on the existing ones. A thread is not an ordinary channel: it has no topic, no permission overwrites and no parent to move it between, and it has archiving, locking, invitability and tags, which no other channel has. Handing a thread to
GuildTextChannelBuildersendstypeand whatever else was set — fields Discord rejects for a thread — and offers none of the ones that actually apply.applied_tagsreplaces the whole set, because that is what Discord does with the field: a tag left out of the list comes off the post. It is reindexed on the way out, since an array with gaps serialises to a JSON object rather than an array and the call comes back refused — which is the kind of thing you only find in production, after filtering a tag list.Found while porting a bot whose petitions live in a forum and move between four tags over their life.
🤖 Generated with Claude Code