fix: markdown editor live refresh#654
Merged
GCWing merged 1 commit intoGCWing:mainfrom May 11, 2026
Merged
Conversation
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
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.
Summary
MarkdownEditorsubscribe toeditor:file-changedevents for the currently opened Markdown file.Root Cause
MarkdownEditorhad metadata polling for external changes, but it did not subscribe to the global file-change event emitted by the file explorer watcher. Agent writes could therefore update the file tree and disk state while the already-open Markdown editor kept showing stale content until the tab was closed and reopened.Validation
pnpm run type-check:webpnpm run lint:webpnpm --dir src/web-ui run test:run