Skip to content

fix: don't mark read-only workspace queries as unsaved - #194

Merged
MathiasVDA merged 1 commit into
mainfrom
claude/project-thread-1mbgj6
Oct 6, 2026
Merged

MathiasVDA merged 1 commit into
mainfrom
claude/project-thread-1mbgj6

Conversation

@MathiasVDA

Copy link
Copy Markdown
Collaborator

Requested by Mathias · project thread

Follow-up to #193 (#187).

Before: after a query opened from a read-only workspace was edited, either by the user or by the parser or formatter when the query ran, its tab showed the unsaved dot, and closing the tab asked whether to save.

After: tabs holding a query from a read-only workspace never count as unsaved. No dot appears, and the tab closes without asking.

How: Tab.hasUnsavedManagedChanges() returns false when the tab's workspace is read-only. Both the tab's dirty marker (TabElements) and the close prompt use this method. The user guide and a patch changeset are updated to match.

The unit tests pass (1679). I have not checked it in a browser.

🤖 Generated with Claude Code

https://claude.ai/code/session_01StQ5dk15ErNgjFnErZ7ce4


Generated by Claude Code

Edits to a query opened from a read-only workspace can never be saved
back, so the tab no longer shows the unsaved dot and closing it no
longer asks to save.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01StQ5dk15ErNgjFnErZ7ce4
@MathiasVDA MathiasVDA self-assigned this Oct 6, 2026
@MathiasVDA
MathiasVDA merged commit 82534ee into main Oct 6, 2026
2 checks passed
@MathiasVDA
MathiasVDA deleted the claude/project-thread-1mbgj6 branch October 11, 2026 19:53
MathiasVDA added a commit that referenced this pull request Oct 11, 2026
Edits to a query opened from a read-only workspace can never be saved
back, so the tab no longer shows the unsaved dot and closing it no
longer asks to save.
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.

2 participants