Repository navigation
Comprehensive migrations - #3268
Merged
Merged
Conversation
texodus
force-pushed
the
perspective-migrate
branch
2 times, most recently
from
November 3, 2026 18:51
8434275 to
03c697c
Compare
Signed-off-by: Andrew Stein <steinlink@gmail.com>
texodus
force-pushed
the
perspective-migrate
branch
from
November 3, 2026 22:43
03c697c to
00502aa
Compare
texodus
marked this pull request as ready for review
November 3, 2026 23:39
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.
This PR adds
perspective-migrate, which upgrades persisted configs written by any release since 2.0.0 to the current schema. It covers engineViewConfigs,ViewerConfigs (<perspective-viewer>save()tokens) andWorkspaceConfigs (saveWorkspace()tokens, including the old lumino<perspective-workspace>layouts).versionfield decides how it's upgraded. Without one, it falls back to an optionalfrom_version, then to 2.0.0. Migrating the output again changes nothing.PluginMigration.perspective-migratecrate.@perspective-dev/client:migrate(), after registering the wasm withinit_server({wasm32, wasm64, migrate}). In JS it ships as a separate wasm; It's only downloaded on the firstmigrate()call, and the CDN bundles register it automatically.migrate(), with no registration needed.perspective.migrate().Breaking
restore(),addPanel()andrestoreWorkspace()reject keys the config format doesn't define. When a rejected config is stamped by another release, the error names that release and points tomigrate().expressions;is None/is not Nonefilter operators;sum not nullandpct sum grand totalaggregates;view.get_config()now emits aggregate names thattable.view()accepts, e.g.lastinstead oflast value.