You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Motivation
Error messages about a node causing an error are currently in the weird situation that we know exactly which node caused the error but have no way to refer to the node. We currently just use the node (schema) name to refer to nodes, which does work but isn't unique.
Description #2749 added the ability to give nodes custom names. We can use these names to help users identify which node caused the error by displaying the node name alongside the schema name.
The text was updated successfully, but these errors were encountered:
Motivation
Error messages about a node causing an error are currently in the weird situation that we know exactly which node caused the error but have no way to refer to the node. We currently just use the node (schema) name to refer to nodes, which does work but isn't unique.
Description
#2749 added the ability to give nodes custom names. We can use these names to help users identify which node caused the error by displaying the node name alongside the schema name.
The text was updated successfully, but these errors were encountered: