You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These versioning numbers are getting weird b/c PD used to only export protocols with 1 schema number, but now is cross-compatible with v3 and v4.
PD when dealing with v3 protocols is now effectively v3.1.x, because the Pause form values have changed to support additional options. (PD I thought we decided to not change the existing values to avoid a migration??)
This means that PD needs a migration from 3.0 to 4, mapping the old Pause form values to new values.
Also I made #5369 without being aware this was going on, so those snapshots need to be updated b/c right now they're snapshots of an incomplete migration. IMO that can happen in this ticket or in that one, whatever's more expedient.
But PD version bump to 4.0.0 #5148 is a blocker to this, because migration functions depend on that number
Current behavior
Import a pre-modules-in-PD protocol with Pause steps, eg protocol-designer/src/load-file/__tests__/fixtures/throughMigrationV0/preFlexGrandfatheredProtocol.json
You'll see a timeline error: "Must either pause for amount of time, until told to resume, or until temperature reached"
Expected behavior
Pause should be migrated to the new values so that whatever was in the existing protocol maps to the new values
The text was updated successfully, but these errors were encountered:
Overview
These versioning numbers are getting weird b/c PD used to only export protocols with 1 schema number, but now is cross-compatible with v3 and v4.
PD when dealing with v3 protocols is now effectively v3.1.x, because the Pause form values have changed to support additional options. (PD I thought we decided to not change the existing values to avoid a migration??)
This means that PD needs a migration from 3.0 to 4, mapping the old Pause form values to new values.
Also I made #5369 without being aware this was going on, so those snapshots need to be updated b/c right now they're snapshots of an incomplete migration. IMO that can happen in this ticket or in that one, whatever's more expedient.
But PD version bump to 4.0.0 #5148 is a blocker to this, because migration functions depend on that number
Current behavior
protocol-designer/src/load-file/__tests__/fixtures/throughMigrationV0/preFlexGrandfatheredProtocol.json
Expected behavior
Pause should be migrated to the new values so that whatever was in the existing protocol maps to the new values
The text was updated successfully, but these errors were encountered: