Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Extensions should be able to define hidden blocks for compatibility #735
Because of changes in the set of blocks between 2.0 and 3.0, we need to provide support for compatibility with older projects. Part of this support involves the ability to define 2.0-compatible blocks that do not show up in the palette, but which can load in a project that uses them.
Extensions cannot yet define hidden blocks.
So, basically hacked blocks :)
I wonder if it would be better to transform old projects to use new, functionally equivalent blocks? That way there's no mysterious 2.0 "legacy" blocks floating around (which will inevitably be backpacked and used in new projects, because people love using hacked blocks).
What about conversions to different ranges? It might be confusing to open an old project in Scratch 3.0 and see something like