-
Notifications
You must be signed in to change notification settings - Fork 3.5k
fix(serializer): preserve block enabled state during deserialization #3950
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -622,7 +622,7 @@ export class Serializer { | |
| position: serializedBlock.position, | ||
| subBlocks, | ||
| outputs: serializedBlock.outputs, | ||
| enabled: true, | ||
| enabled: serializedBlock.enabled ?? true, | ||
| triggerMode: | ||
|
Comment on lines
624
to
626
|
||
| serializedBlock.config?.params?.triggerMode === true || | ||
| serializedBlock.metadata?.category === 'triggers', | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change will require updating the existing unit test that currently asserts the buggy behavior.
apps/sim/serializer/tests/serializer.extended.test.tshas a case (should deserialize enabled status correctly) whereenabled: falseis expected to deserialize totrue; after preservingenabled, it should assertfalse(and ideally add a separate assertion for the backward-compat default whenenabledis missing).