Skip to content

fix: allow table deletion confirmation requests T6924 - #145

Merged
nichenqin merged 1 commit into
mainfrom
fix/deleted-table-confirmation-request
Sep 18, 2026
Merged

nichenqin merged 1 commit into
mainfrom
fix/deleted-table-confirmation-request

Conversation

@nichenqin

Copy link
Copy Markdown
Contributor

The deleted-table collaborator runner aborts every request containing the target table ID. That now also blocks the table-detail GET used to distinguish deletion from a temporarily omitted provisioning table, making correct network-error handling look like a deletion-recovery regression.

Allow only that GET to reach the backend via route.fetch/fulfill; stale record and snapshot requests remain aborted. Keep all existing deletion, navigation, routing and page-error assertions. Update the case documentation to explain the distinction.

Validation: pnpm check passed. Browser acceptance should compare the original unfixed revision and the updated product commit with this runner.

Unblocks the harness failure reported in teableio/teable-ee#3419 (T6660); the original deletion case is T6924.

@nichenqin
nichenqin merged commit 4a9bd45 into main Sep 18, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant