fromSb3: Fix loading undefined sb3Block.next #146
Merged
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.
Development:
See #143 for some technical discussion.
Best to view the commits separately, as they are independent changes, though they affect the same area of code.
next
on blocks in a project.json not crashfromSb3
. This may be a omission by a minifier used in the demo project, rather than something Scratch itself will ever serialize, though Scratch handles deserializing undefinednext
just fine, so sb-edit should too.blockWithNext
is sometimes called without itsparentId
argument so we just make itparentId?: string
instead ofparentId: string | undefined
. AndgetBlockScript
, previously called once for each script in a target, is now called just once for each target, becausegetBlockScript
does not care which script you're about to get, and is structured to make all scripts available. (It's a currying function, so now we use it like one!)Tested manually with the project shared in #141, WebOMatic!.