Debug warning in Blockly 12: blockly_compressed.js:164 Blockly.Workspace.getAllVariables was deprecated in v12 and will be deleted in v13. Use Blockly.Workspace.getVariableMap().getAllVariables instead.

[Michael Scherotter]

I have code that I just upgraded to Blockly 12 where I call 
Blockly.Xml.domToWorkspace(xml, this._workspace);

The code works fine, but I now get a warning in the debugger:

blockly_compressed.js:164 Blockly.Workspace.getAllVariables was deprecated in v12 and will be deleted in v13. Use Blockly.Workspace.getVariableMap().getAllVariables instead.

warn$$module$build$src$core$utils$deprecation@blockly_compressed.js:164
getAllVariables@blockly_compressed.js:1277
domToBlockInternal$$module$build$src$core$xml@blockly_compressed.js:319
$.domToWorkspace$$module$build$src$core$xml@blockly_compressed.js:312

It seems to work fine.Any suggestions?Michael

[Maribeth Moffatt]

You don't need to do anything, this is a warning that we need to fix within Blockly. You can follow along with our progress here https://github.com/google/blockly/issues/8945 and the fix will be included in a future patch release of Blockly. This warning should have no ill effect on the rest of your application.

Best,

Maribeth

[Michael Scherotter]

Thanks!

Michael

[Michael Scherotter]

Past that, the upgrade to Blockly 12 was very smooth.

Great job, Blockly team!

Thanks,
Michael

On Tuesday, May 27, 2025 at 4:24:26 PM UTC-7 mari...@google.com wrote:

[Johnny Oshika]

I agree, the upgrade to Blockly 12 was very smooth, but my application is left with lots of these warnings:

Blockly.Workspace.getVariableById was deprecated in v12 and will be deleted in v13. Use Blockly.Workspace.getVariableMap().getVariableById instead.

Particularly noticeable is when my application's unit tests run, as I see dozens of these warnings, which makes it hard to separate out real errors.

Looking forward to a fix landing soon. I'll follow this issue.