Skip to content

Add snapshot.rebase(newBaseSnapshot, changes) - #64679

Open
Wesley Wigham (weswigham) wants to merge 1 commit into
microsoft:mainfrom
weswigham:snapshot-rebase
Open

Wesley Wigham (weswigham) wants to merge 1 commit into
microsoft:mainfrom
weswigham:snapshot-rebase

Conversation

@weswigham

Copy link
Copy Markdown
Member

Much like Snapshot.update, Snapshot.rebase allows creating a new snapshot based on an old one, except Snapshot.rebase uses data from two old snapshots to make a new snapshot.

Given const rebased = old.rebase(new), we take the synthetic FS stored in old and reapply it over new's existing FS data, if any (akin to a git rebase) to produce a new snapshot. (Do note: a full FS override in old will still replace the FS in new - it's a full replacement! The only thing that'd change here is refreshing underlying real FS files!) Optionally, we also take normal update arguments, if there are additional settings on the resulting snapshot update you wish to alter - snapshot.rebase(snapshot, settings) is basically identical to snapshot.update(settings).

What does this let you do? Well, for our LSP API users,

const initial = api.getCurrentLanguageServiceSnapshot()
const updated = initial.update(/* layer on custom additions */)
// fetch diagnostics for updated or whatever else you want
// actual disk/editor updates LSP snapshot
// ... later ...
const newInitial = api.getCurrentLanguageServiceSnapshot()
const reappliedUpdate = updated.rebase(newInitial) // no need to send over identical FS contents
// work with reappliedUpdate without needing to recalculate synthetic FS state

allowing you to retain the same synthetic FS structure you already generated across multiple real-FS updates without a lot of repeated traffic over the API protocol.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Missed invalidations can retain stale target contents or removed files in rebased snapshots.

3 open findings
What changed in this PR

Adds Snapshot.rebase to reuse synthetic filesystem changes over another snapshot without resending file contents.

Changes:

  • Adds server, protocol, async, sync, and generator support.
  • Implements filesystem composition and change notifications.
  • Tests rebasing, invalidation, disposal, and auto-import behavior.
File Description
tsc/​internal/​api/​session.go Handles rebase requests.
tsc/​internal/​api/​session_requestfilesystem_test.go Tests self-rebase incremental state.
tsc/​internal/​api/​session_rebase_test.go Tests composition and snapshot lifetimes.
tsc/​internal/​api/​session_rebase_changes_test.go Tests invalidation and update parity.
tsc/​internal/​api/​session_completion_test.go Tests rebase auto-import preparation.
tsc/​internal/​api/​requestfilesystem/​requestfilesystem.go Composes rebased filesystems.
tsc/​internal/​api/​requestfilesystem/​rebase_test.go Tests input immutability.
tsc/​internal/​api/​requestfilesystem/​pathtree.go Preserves removed-path metadata.
tsc/​internal/​api/​requestfilesystem/​filechanges.go Generates rebase change notifications.
tsc/​internal/​api/​requestfilesystem/​filechanges_test.go Tests notifications and path casing.
tsc/​internal/​api/​proto.go Defines the rebase protocol.
packages/​typescript/​test/​sync/​api.test.ts Adds generated sync coverage.
packages/​typescript/​test/​sync/​api-generators.test.ts Tests generator parity.
packages/​typescript/​test/​async/​api.test.ts Adds async rebase coverage.
packages/​typescript/​src/​api/​sync/​api.ts Adds generated sync and generator APIs.
packages/​typescript/​src/​api/​proto.generated.ts Adds generated protocol types.
packages/​typescript/​src/​api/​async/​api.ts Exposes the async rebase API.

🧠 Review effort: Balanced


💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +71 to +72
if previousFallback != requestFallbackMissing {
addChangeAndAliases(child.fallbackPath, lsproto.FileChangeTypeDeleted)
paths: paths,
}
changed := addRebaseFileChanges(fileChanges, source, baseFileSystem, result)
if source.kind == KindFull && (!HasFullFileSystem(baseFileSystem) || changed) {
if fileSystem == nil {
fileSystem = s.FS()
}
fileSystem = requestfilesystem.Rebase(source.fileSystem, fileSystem, &fileChanges)
updatedSnapshot := session.snapshots[updated.Snapshot].snapshot
updatedProject := updatedSnapshot.ProjectCollection.GetProject(project.ID("/a/tsconfig.json"))
assert.Assert(t, updatedProject.GetProgram() != baseProgram)
assert.Equal(t, updatedProject.ProgramUpdateKind, project.ProgramUpdateKindCloned)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Related to my comment on session.go: this only hits ProgramUpdateKindCloned here because it's a self-rebase (Snapshot: params.Snapshot, NewSnapshot: params.Snapshot). In TestRebaseSnapshot (rebasing a layered snapshot with extra files onto a new getCurrentLanguageServerSnapshot()), the project ends up with ProgramUpdateKindNewFiles.

}
apiRequest.FileSystem = fileSystem
apiRequest.ReplaceFileSystem = changes.FileSystem != nil && changes.FileSystem.Kind == requestfilesystem.KindFull
snapshot, err := s.snapshotHost.CloneSnapshot(ctx, target.snapshot, fileChanges, apiRequest)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In our case source.fileSystem has hundreds of virtual .ngtypecheck.ts files that don't exist in target.snapshot. Since handleRebaseSnapshot clones from target.snapshot and marks all of source.fileSystem's files as Created relative to target, will every rebase onto a new snapshot invalidate target's tsconfig file list and force compiler.NewProgram instead of ReuseProgram (ProgramUpdateKindCloned) when a user edits a single .ts file?

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants