Serializing a stack of blocks only outputs the first block
See original GitHub issueProblem statement
Dragging a stack of blocks out of the Toolbox only copies the top block in the stack.
Expected Behavior
The entire stack should be dragged out.
Actual Behavior
Only the first block in the stack is dragged out.
Steps to Reproduce
- Open the local copy of tests/playground.html on develop branch
- Switch to test blocks
- Try to drag out the stack in the drag category
Stack Traces
Replace with error stack trace.
Operating System and Browser
Desktop Chrome
Additional Information
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Serialization | Blockly - Google Developers
Individual stacks/top-level blocks are deserialized in an arbitrary order. Type is deserialized. This triggers the block's init method, mixes in ...
Read more >Java serializing object with ObjectOutputStream works once ...
I am using this static class as a way to serialize objects into strings before sending / using them in various ways. However...
Read more >Add JSON serialization hooks to the lists_getIndex block #6136
The block should have a JSON serialization hook including data about whether it is a stack or value block. Additional context.
Read more >wordpress/block-serialization-default-parser
This library contains the default block serialization parser implementations for WordPress documents. It provides native PHP and JavaScript…
Read more >RECURSIVE STACK-BASED SERIALIZATION OF ...
Abstract: A data-serialization system initially uses a recursive serialization algorithm to serialize a hierarchy of nested data objects by ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like #2080 broke it by changing the node type for next blocks. @NeilFraser
@VoxelPerfect done: https://github.com/google/blockly/releases/tag/1.20181105.0