Triggering a direct edit in the explorer on elements without a declared name displays an initial value, instead of an empty string.
This breaks the implicit contract of direct edit, which shouldn't perform any edition if the user simply validates the initial value presented to them.
In the example below, triggering a direct edit on a Dependency without a declared name prompts Dependency as initial direct edit value.
In the example below, triggering a direct edit on a Dependency without a declared name and with a short name prompts <short name> Dependency as initial direct edit value.
Note that validating this initial value will update the Dependency's declared name to <abc> Dependency, while its short name will remain <abc>.
This is clearly wrong, since it leads to a duplicated short name.
Triggering a direct edit in the explorer on elements without a declared name displays an initial value, instead of an empty string.
This breaks the implicit contract of direct edit, which shouldn't perform any edition if the user simply validates the initial value presented to them.
In the example below, triggering a direct edit on a
Dependencywithout a declared name promptsDependencyas initial direct edit value.In the example below, triggering a direct edit on a
Dependencywithout a declared name and with a short name prompts<short name> Dependencyas initial direct edit value.Note that validating this initial value will update the
Dependency's declared name to<abc> Dependency, while its short name will remain<abc>.This is clearly wrong, since it leads to a duplicated short name.