As of now the component triggers onChange with selectedNode as soon as a tag input matches a node (or nodes when using wildcard). This can the trigger unwanted selections, e.g. stating a valid selection before a the wanted tag is actually finalized.
Consider adding functionality (e.g. pushing enter) to ensure actively selection of a tag.
Example of use case:
If the component is used to actively select based on selected nodes, the SmartNodeSelector will provide onChange with selectedNodes-array as long as tags matches one or more nodes. This is most common if the user writes tags character by character. E.g. "TEST:TEST1" and "TEST:TEST12" can give issues, as user might want to write "TEST:TEST12", but onChange with tag "TEST:TEST1" will be triggered before the user is finished writing wanted tag.
Thereby the user looses control of actively selecting tags when using the selector for updating/selecting nodes.
As of now the component triggers
onChangewith selectedNode as soon as a tag input matches a node (or nodes when using wildcard). This can the trigger unwanted selections, e.g. stating a valid selection before a the wanted tag is actually finalized.Consider adding functionality (e.g. pushing enter) to ensure actively selection of a tag.
Example of use case:
If the component is used to actively select based on selected nodes, the
SmartNodeSelectorwill provideonChangewithselectedNodes-array as long as tags matches one or more nodes. This is most common if the user writes tags character by character. E.g. "TEST:TEST1" and "TEST:TEST12" can give issues, as user might want to write "TEST:TEST12", butonChangewith tag "TEST:TEST1" will be triggered before the user is finished writing wanted tag.Thereby the user looses control of actively selecting tags when using the selector for updating/selecting nodes.