feat(editing)!: scope recent-messages picker to a chosen channel - #123
Merged
Conversation
The load dialog's "recent messages" picker now requires the user to pick a channel first (reusing the existing `loadChannels`), then calls `loadRecentMessages(channelId)` scoped to that one channel instead of scanning the whole workspace. Changing the channel re-fetches; loading/empty/error states render per channel. The paste-a-link path is unchanged. BREAKING CHANGE: `EditingConfig.loadRecentMessages` now takes a `channelId` argument: `(channelId: string) => Promise<RecentMessage[]>`. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
block-kitchen | 6ed0ad7 | Commit Preview URL Branch Preview URL |
Jun 30 2026, 05:00 AM |
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.
What
The editor's load dialog now scopes its "recent messages" picker to a single channel the user picks, instead of fetching recent editable messages across the whole workspace.
EditingConfig.loadRecentMessagesnow takes achannelId:(channelId: string) => Promise<RecentMessage[]>.loadChannelsprop, no new prop) under "or pick a recent message". Only after a channel is selected does it callloadRecentMessages(channelId)and render that channel's results.loadChannelsfailures).onLoadMessage) is unchanged.Breaking change
loadRecentMessagesgains a requiredchannelIdargument. Hosts passing it must update the signature.Demo
The mocked-Slack demo filters its in-memory fixtures to the selected channel; fixtures span channels so each editability outcome stays demonstrable per channel.
Tests / docs
test/load-message-dialog.test.tsx: requires a selection before listing, scopes per channel, re-fetches on change, empty + thrown-error states.Verification
tscclean, full suite (359 existing + 3 new) green, biome clean.Out of scope: the host (tightknit-app) side, whose engine already accepts an optional
channelIdand will pass the selected channel once this version ships.🤖 Generated with Claude Code