Create channel and Create category (pulled forward from server administration) #663

Closed
opened 2026-11-15 18:35:03 +00:00 by charles · 1 comment
Owner

Asked by Charles, 2026-11-15: "we still can't create channels".

Creating channels and categories was left out of Daily use on purpose: docs/parity/dailyuse.md lists "Guild menu | Create channel, Create category | later (7) | guild administration". This issue pulls that one slice forward from sub-project 7 (server administration).

Wanted (match the original; read its code in the fork: the channel create modal, the category create modal, and where they are opened from).

  • Entry points as in the original: the community header menu ("Create channel", "Create category"), the "+" on a category row, the channel list's empty-area and category context menus. Shown only with MANAGE_CHANNELS.
  • The create-channel modal: channel type choices the original offers (text, voice, forum/link, … whatever it has), name with the original's name normalisation and validation, the category it is created under, and any other field the original's modal has. The create-category modal: name.
  • API: POST /guilds/{id}/channels in fluxer-api, proto types, the request through the runtime like other Daily-use actions, errors shown as the original shows them (permission, limit reached, invalid name).
  • After creation: the channel appears from the gateway CHANNEL_CREATE event (not from the response alone) and, as the original does, the client opens the new text channel.
  • Dev server: support the endpoint so tests run without the live server.
  • Out of scope: editing, deleting, reordering channels, permission overwrites (still sub-project 7). Move the parity row from "later (7)" to done and add rows for what stays later.
**Asked by Charles, 2026-11-15:** "we still can't create channels". Creating channels and categories was left out of Daily use on purpose: `docs/parity/dailyuse.md` lists "Guild menu | Create channel, Create category | later (7) | guild administration". This issue pulls that one slice forward from sub-project 7 (server administration). **Wanted (match the original; read its code in the fork: the channel create modal, the category create modal, and where they are opened from).** - Entry points as in the original: the community header menu ("Create channel", "Create category"), the "+" on a category row, the channel list's empty-area and category context menus. Shown only with MANAGE_CHANNELS. - The create-channel modal: channel type choices the original offers (text, voice, forum/link, … whatever it has), name with the original's name normalisation and validation, the category it is created under, and any other field the original's modal has. The create-category modal: name. - API: `POST /guilds/{id}/channels` in fluxer-api, proto types, the request through the runtime like other Daily-use actions, errors shown as the original shows them (permission, limit reached, invalid name). - After creation: the channel appears from the gateway `CHANNEL_CREATE` event (not from the response alone) and, as the original does, the client opens the new text channel. - Dev server: support the endpoint so tests run without the live server. - Out of scope: editing, deleting, reordering channels, permission overwrites (still sub-project 7). Move the parity row from "later (7)" to done and add rows for what stays later.
Author
Owner

In nightly 2026.1115.335.

In nightly 2026.1115.335.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#663
No description provided.