Renaming the node by leaving the name field empty causes unexpected behavior

[khashashin]

Renaming the node by leaving the name field empty causes unexpected behavior

[janober]

Fix got released with [email protected]

[Joffcom]

Hey @khashashin,

I have created ADO-2226 as the internal ticket to get this one resolved, If no name is inputted it should really just keep the orginal name.

[janober]

Thanks for reporting this.
Users should, however, not be able to create nodes without names. After all, would it then for example be impossible to reference data from it via expressions. Additionally would a million other things break inside of n8n.
Anyway, it should for sure display an error message when a user tries to do that and ultimately not allowing it. So for sure something we have to fix.

[khashashin]

Yeah, I understand it is too late for such a change since it would result in a breaking change. However, I believe allowing the use of names in expressions was not the best idea. Names are subject to change, often based on user preference, which can lead to broken assignments in other expressions.

[janober]

This like any other choice, it has advantages and disadvantages. We discussed it a while ago especially regarding expressions and we came to the conclusion that there are still more advantages.

Generally should it not cause any problems when a node is renamed, as all expressions in the workflow get also updated automatically as well.