feat(commands/util/walkthrough): add Other options and editable answers - #60
Open
phorcys420 wants to merge 7 commits into
Open
feat(commands/util/walkthrough): add Other options and editable answers#60phorcys420 wants to merge 7 commits into
phorcys420 wants to merge 7 commits into
Conversation
railway-app
Bot
temporarily deployed
to
Discord bot (Codercord) / production
August 12, 2026 07:29
Inactive
railway-app
Bot
temporarily deployed
to
Discord bot (Codercord) / production
August 12, 2026 07:32
Inactive
railway-app
Bot
temporarily deployed
to
Discord bot (Codercord) / production
August 12, 2026 07:36
Inactive
railway-app
Bot
temporarily deployed
to
Discord bot (Codercord) / production
August 12, 2026 07:37
Inactive
railway-app
Bot
temporarily deployed
to
Discord bot (Codercord) / production
August 12, 2026 07:41
Inactive
railway-app
Bot
temporarily deployed
to
Discord bot (Codercord) / production
August 12, 2026 07:46
Inactive
…coder and code-server
…it while editing platform
phorcys420
force-pushed
the
phorcys/walkthrough-other-and-edit
branch
from
August 13, 2026 00:31
102ca56 to
3f92998
Compare
railway-app
Bot
temporarily deployed
to
Discord bot (Codercord) / production
August 13, 2026 00:33
Inactive
Cache guild command-mention lookups and resolve edit permissions from the interaction payload instead of fetching the guild member, so a selection or edit re-renders without waiting on Discord REST calls.
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
1 participant
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.
Implements the two remaining unticked items from #1.
Changes
Otheroptions for every questionAdds an
Other(❓) option to the product and OS-family selectors (category already had one). Kept static to match the existing categoryOtherand the stateless select-menu design (no modal/free-text, consistent with the modal approach discarded in #1).Editable answers instead of a back button
walkthrough:field:<index>:<...answers>, so a click carries enough state to reopen that question. No persistent store, stays stateless.handleFieldButtonreopens the clicked field's selector instead of replying that it can't be edited.handleSelectiongained aneditbranch: an edit selection replaces that answer in place and leaves later answers intact; any remaining steps continue as usual.canMemberInteractWithThreadhelper (thread OP orManageChannels). Unauthorized clicks get an ephemeral deny. The normal forward flow is unchanged.bun format,bun lint, andbunx tsc --noEmitall pass.Closes #1.
Decision log
Othervs free-text. Chose static options for parity with the existing categoryOtherand to avoid introducing state or a modal (the modal approach was explicitly discarded in Issue walkthrough #1). Editing anOtherfield just reopens the selector.buildMessagestill renders the next unanswered step, so an incomplete walkthrough resumes naturally after an edit.canMemberInteractWithThread(OP or Manage Channels) and applied it to both the field button and the edit-select interaction, so a bystander can't drive the edit selector once it's visible. The normal forward selection flow was left ungated to avoid changing existing behaviour.Generated by Coder Agents on behalf of @phorcys420.