Skip to content

Releases: google/blockly

blockly-v10.3.1

17 Jan 21:22
1ba0e55
Compare
Choose a tag to compare

What's Changed

Bug fixes 🐛

  • fix: triggering flyout show from field render causing infinite loop by @BeksOmega in #7784
  • fix: cancelling all renders on triggering queued renders by @BeksOmega in #7787
  • fix: first block dragged from flyout will have same id by @maribethb in #7788

Full Changelog: blockly-v10.3.0...blockly-v10.3.1

blockly-v11.0.0-beta.1

08 Jan 18:49
Compare
Choose a tag to compare
Pre-release

This is the second in what we expect will be a series of beta releases for the future v11 of Blockly. See information about the Blockly v11 Beta Program.

Highlights in v11.0.0-beta.1

The only new change in -beta.1 is a fix for an issue reported about the new generator type declarations in -beta.0. Thanks to @clementcontet for spotting and reporting this error!

What's Changed

Bug fixes 🐛

  • fix(generators): Fix generator type declarations by @cpcallen in #7750

Full Changelog: blockly-v11.0.0-beta.0...blockly-v11.0.0-beta.1

blockly-v11.0.0-beta.0

23 Dec 23:40
Compare
Choose a tag to compare
Pre-release

This is the first in what we expect will be a series of beta releases for the future v11 of Blockly.

Blockly v11 Beta Program

We have a fairly large backlog of breaking changes that we've been holding on to, and we are planning to publish a series of betas ad hoc as those changes are finished and ready for you to test. We want to get these out to you as soon as possible, for two reasons:

  • So that you can prepare modifications to your projects as required in response to the breaking changes we're planning to include in v11.
  • So that you can give us early feedback about issues you encounter. We're interested in reports of any kind of bug, of course, but we're especially interested in hearing if a breaking change we're planning for v11 turns out to create intractable difficulties in upgrading your project(s).

It is quite likely that work on Blockly v10, including backwards-compatible bug fixes and/or new features, will continue in parallel with work on the less backwards-compatible changes we're planning for v11. We expect that in most cases each v11 beta will be up-to-date with all the latest v10 updates, but we can't make any such guarantees. As such, you should continue using v10 in production, since bugs will get fixed in v10 first, and v11 will probably introduce exciting new bugs—though with your help we hope to fix most of them before v11.0.0 is officially released.

Highlights in v11.0.0-beta.0

The only breaking change in this release is that we're finally publishing accurate TypeScript typings for the generators! 🎉

The generators were migrated to TypeScript in v10.3.0, concluding our work to migrate the core Blockly codebase from JavaScript to TypeScript. The new TypeScript implementation is (intended to be) functionally the same but a change in published typings is likely to break existing projects; to avoid this we opted to continued to publish the same hand-written .d.ts files for the generator entrypoints (e.g. blockly/javascript) that we have been using until now.

Previously the dartGenerator, luaGenerator, javascriptGenerator, phpGenerator, and pythonGenerator exports (from the blockly/dart, blockly/lua, blockly/javascript, blockly/php and blockly/python entrypoints respectively) were being typed any.
(In hindsight we should probably have declared them as unknown, obliging TS developers to use explicit casts.) Now their types are correct. There is no change to their runtime behaviour, but developers who have written code in TypeScript that manipulates generators (adding custom block generator functions, for example) may find they need to correct type errors in their code in order for it to compile correctly with Blockly v11.

Notably, block generator functions to be installed in the javascriptGenerator.forBlock dictionary should be typed

(block: Blockly.Block, generator: javascript.JavascriptGenerator) => [string, javascript.Order] | string | null

—and similarly for each of the other four languages we support.

Note that in most cases the return type for any particular generator function can be either [string, javascriptOrder] (for expression blocks), string (for statement blocks), or null (for blocks that do not directly emit code).

What's Changed

Breaking changes 🛠

Bug fixes 🐛

  • fix: Remove double spaces in translation instructions. by @NeilFraser in #7704
  • fix: updated mocha tests to display error messages by @btw17 in #7706
  • fix: prevent flyout block highlighting during workspace drag by @neerajkumarc in #7720

New Contributors

Full Changelog: blockly-v10.3.0...blockly-v11.0.0-beta.0

blockly-v10.3.0

07 Dec 23:06
26ee8cf
Compare
Choose a tag to compare

What's Changed

New features ✨

Bug fixes 🐛

Cleanup ♻️

  • refactor(generators): Migrate JavaScript generators to TypeScript by @cpcallen in #7602
  • refactor(generators): Migrate Python generators to TypeScript by @cpcallen in #7617
  • refactor(generators): Migrate Dart generators to TypeScript by @cpcallen in #7646
  • refactor(generators): Migrate Lua generators to TypeScript by @btw17 in #7654
  • refactor(generators): Migrate PHP generators to TypeScript by @cpcallen in #7647

Reverted changes ⎌

Other changes

New Contributors

Full Changelog: blockly-v10.2.2...blockly-v10.3.0

blockly-v10.2.2

09 Oct 17:47
925a7b9
Compare
Choose a tag to compare

What's Changed

Other changes

Full Changelog: blockly-v10.2.1...blockly-v10.2.2

blockly-v10.2.1

02 Oct 20:34
ead46e7
Compare
Choose a tag to compare

What's Changed

Other changes

Full Changelog: blockly-v10.2.0...blockly-v10.2.1

blockly-v10.1.3

24 Aug 18:32
e459984
Compare
Choose a tag to compare

This patch release rolls back a change to the serialization of insertion markers. The change set blocks to be insertion markers after their extra state was loaded, rather than before.

The issue was reported in google/blockly-samples#1856 and this release rolls back the change. We will roll this change forward at our next breaking release.

What's Changed

Other changes

Revert "fix: insertion marker's next blocks become real block (#7384)"

Revert "feat: Insertion marker json deserialization 7316 ( #7364 )" "

Full Changelog: blockly-v10.1.0...blockly-v10.1.3

blockly-v10.1.2

14 Aug 17:19
18ee0ec
Compare
Choose a tag to compare

What's Changed

Bug fixes 🐛

New Contributors

Full Changelog: blockly-v10.1.1...blockly-v10.1.2

blockly-v10.1.1

10 Aug 21:17
7bca438
Compare
Choose a tag to compare

What's Changed

Other changes

  • Revert "fix: removed X & Y from toolbox.ts and replaced movBy to moveTo" by @BeksOmega in #7375

Full Changelog: blockly-v10.1.0...blockly-v10.1.1

blockly-v10.1.0

10 Aug 16:52
80b1b44
Compare
Choose a tag to compare

What's Changed

Deprecations 🧹 - APIs that may be removed in future releases

  • fix: Restore HSV_SATURATION and HSV_VALUE accessors and deprecate by @cpcallen in #7249

New features ✨

Bug fixes 🐛

  • fix: set flyout visbility on calling setExpanded by @jibranabsarulislam in #7199
  • fix(tests): Make test imports correct and more consistent by @cpcallen in #7260
  • fix: disposing workspace comments. by @johnnesky in #7264
  • fix: add compose and decompose errors to mutator icon by @BeksOmega in #7289
  • fix(generators): Changes to exports and access controls for TypeScript compatibility by @cpcallen in #7295
  • fix: Correct errors in HSV_SATURATION, HSV_VALUE accessors by @cpcallen in #7297
  • fix: have icons use the new render management system by @BeksOmega in #7296
  • fix: make deserialization use the new render management system by @BeksOmega in #7306
  • fix: make insertion markers use new render management system by @BeksOmega in #7307
  • fix: remove old render method by @BeksOmega in #7308
  • fix(blocks): boolean variable block wrong shape for zelos by @zfangqijun in #7335
  • fix(build): support running Blocky locally on Windows machines by @abdul-alhasany in #7281
  • fix: removed X & Y from toolbox.ts and replaced movBy to moveTo by @varshneydevansh in #7333
  • fix: deprecate render functions by @BeksOmega in #7359
  • fix: connect animation persisting by @BeksOmega in #7365

New Contributors

Full Changelog: blockly-v10.0.1...blockly-v10.1.0