Skip to content

Conversation

@DNin01
Copy link
Member

@DNin01 DNin01 commented Feb 11, 2026

Problem

The ESLint rule no-useless-assignment recently became recommended and is now checked for in our repository. As a result, some code now creates error messages. These errors happen when a variable is assigned a value that is never read later or is guaranteed to be reassigned before it is read.

You can learn more about this on the ESLint Docs.

Changes

These errors were fixed. In the process, a bug in editor-theme3 where the addon always use the old Blockly reference for FieldNote was fixed. The 10 other changes should have no effect.

Checks

ESLint checks succeed on the changes.

@DNin01 DNin01 requested review from Hans5958 and mxmou February 11, 2026 19:57
@DNin01 DNin01 added scope: meta Related to the meta of the development (repository, store, etc) scope: development Related to developing, documentation, DevEx, etc. labels Feb 11, 2026
@DNin01 DNin01 marked this pull request as ready for review February 11, 2026 19:57
@Samq64
Copy link
Member

Samq64 commented Feb 11, 2026

It might be a good idea to pin the ESLint version to 10.x and update it on our own schedule.

let FieldNote;
if (Blockly.registry) FieldNote = Blockly.registry.getClass(Blockly.registry.Type.FIELD, "field_note");
FieldNote = Blockly.FieldNote;
else FieldNote = Blockly.FieldNote;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOW all addons support the new Blockly. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

scope: development Related to developing, documentation, DevEx, etc. scope: meta Related to the meta of the development (repository, store, etc)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants