Repository navigation
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideServer-info requests now report the embedded web bundle version via Sequence diagram for version-aware web server-info requestsequenceDiagram
participant WebApp
participant Server
WebApp->>Server: getServerInfo()
Note over WebApp,Server: Headers: X-Platform: web#59; Client-Version: WEB_CLIENT_VERSION
Server-->>WebApp: ServerInfo with enable_database_history
WebApp->>WebApp: Use enable_database_history
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
appflowy
marked this pull request as ready for review
September 28, 2026 08:23
appflowy
added a commit
that referenced
this pull request
Sep 28, 2026
* feat: add database version history previews and restore * fix: harden database history restore and synchronization * fix: preserve restore consumers and recover deferred synchronization * fix: address database history sync and selection review * fix: refresh sidebar after database history restore * fix: keep reopened database history visible after restore recovery * fix: retain authoritative sidebar refresh after database restore * fix: apply remote database restores independently of history UI * fix: recover database aggregates from remote root version changes * fix: block background interaction during database restore * fix: refresh dependent views after database restores Invalidate relation and rollup caches after restores and rebind mounted dependent observers. Guard stale asynchronous loads and cover repeated restores across relation labels, formulas, filters, and sorts. * fix: notify database restores and discard retired client updates * fix: repair database history CI failures - Enable the database history restore permission fence in web CI so the backend advertises database history to the e2e suite - Expect the initial-hydration flag when rediscovering a restored database - Allow the first feed discussion mount more time on cold CI workers - Apply lint padding fixes to database test files Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * fix: keep restore notice focus when an interrupted editor remounts A peer restore can remount the in-progress cell editor after the "Database restored" notice opens. The editor's autofocus takes focus, and MUI's focus trap returns it to the dialog frame rather than the acknowledgement button, so Enter no longer dismisses the notice. Forward focus that lands on the dialog frame to the confirm button. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * refactor: gate database history on a single server capability Drop the separate enable_database_history_version_ui flag. The web client now enables database history (menu entry, preview and restore) from enable_database_history alone; a missing flag still means disabled. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * fix: stop hidden block controls and filter toggle from flaking e2e Hover controls: until the editor's mousemove handler positions the strip, it sits invisible at its static position over the first block and still receives pointer events, swallowing clicks and hovers there (subpage-creation hover timed out on it). Ignore pointer events until the handler enables them. rollup-final-parity: wait for the auto-expanded conditions bar instead of clicking the filter button when the chip is not yet visible, which collapsed the bar while it was still expanding. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * fix: keep cross-tab document sync per keystroke and lossless The database restore barrier gated every collab type: with beforeSend configured, enqueueOutboxUpdate skipped its synchronous sibling-tab fan-out and immediate send for documents too, broadcasting only after the IndexedDB commit. Keystrokes then reached follower tabs in bursts, and the follower read BroadcastChannel collab messages through last-value React state, which keeps only the final message of a burst. Yjs parked every later update behind the lost one, freezing the follower at a prefix (tab_sync.spec.ts failed on 7 of 14 PR runs vs 0 of 39 on main). - Apply the restore barrier only to Database and DatabaseRow updates. - Deliver every BroadcastChannel collab message to the per-object incoming queue in arrival order instead of through last-value state. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * fix: report web bundle version to server-info (#589) * fix: report web bundle version to server-info * fix: set web client fallback version to 0.18.6 --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Server-info requests identify the web platform but omit the client version, so the server cannot enable database history selectively for web 0.18.6 and later. Send the version embedded in the loaded bundle as
Client-Version; an older browser tab continues to report the version it actually runs.Source builds without
APPFLOWY_WEB_VERSIONuse the hardcoded0.18.6fallback, meeting the database-history web version floor. Builds providingAPPFLOWY_WEB_VERSIONreport their embedded build version.This is a companion to the server's database-history version checks and is based on #549. The UI continues to follow the returned
enable_database_historycapability.Validation: all 74 compatibility and HTTP client tests passed, including the request-header assertion.
pnpm type-check, source ESLint, and diff checks passed.Summary by Sourcery
Report the embedded web client version in server-info requests to enable accurate server capability negotiation.
Bug Fixes:
Enhancements:
Documentation:
Tests: