Skip to content

fix(playground): refresh file tree after HTTP imports update mq.lock - #1995

Merged
harehare merged 1 commit into
mainfrom
fix/playground-refresh-file-tree-after-http-import
Jul 11, 2026
Merged

fix(playground): refresh file tree after HTTP imports update mq.lock#1995
harehare merged 1 commit into
mainfrom
fix/playground-refresh-file-tree-after-http-import

Conversation

@harehare

Copy link
Copy Markdown
Owner

Summary

HTTP imports write/update mq.lock directly in OPFS, bypassing the file tree's own write path, so the tree was left stale after execution. Also adds a lock icon for mq.lock and bumps mq-web to 0.6.5.

Type of Change

  • 🐛 Bug fix
  • ✨ New feature
  • ♻️ Refactor
  • 📝 Documentation
  • ⚡ Performance
  • ✅ Test
  • 📦 Build / dependencies
  • 👷 CI

Checklist

  • I ran cargo fmt and cargo clippy and addressed any warnings
  • I ran just test-all and all tests pass
  • I added or updated tests covering this change
  • I updated relevant documentation (/docs, crate README.md) if needed
  • I added a changelog entry if this is a user-facing change

Additional Context

HTTP imports write/update mq.lock directly in OPFS, bypassing the file
tree's own write path, so the tree was left stale after execution.
Also adds a lock icon for mq.lock and bumps mq-web to 0.6.5.
@harehare
harehare force-pushed the fix/playground-refresh-file-tree-after-http-import branch from af02228 to 525524d Compare July 11, 2026 14:15
@harehare
harehare merged commit 417af93 into main Jul 11, 2026
9 checks passed
@harehare
harehare deleted the fix/playground-refresh-file-tree-after-http-import branch July 11, 2026 14:26
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