Bug: machine with unconventional targets can be imported/exported but breaks editor

[josephfh]

XState version

XState version 5

Description

As title. Console error message from the editor:

_app-af856e1a62dd54fe.js?dpl=dpl_GWbyzzohyQsejJrC4Mqt46f2wrhK:615 Error: org.eclipse.elk.core.UnsupportedGraphException: The source or the target of edge ElkEdge "target-i8av66y1sqc" ElkNode "i8av66y1sqc" (0,0 | 157.8559079094802,89.06250574191411) -> ElkNode "5se3sw28mdg" (0,0 | 0,0) could not be found. This usually happens when an edge connects a node laid out by ELK Layered to a node in another level of hierarchy laid out by either another instance of ELK Layered or another layout algorithm alltogether. The former can be solved by setting the hierarchyHandling option to INCLUDE_CHILDREN.

Expected result

A warning about incorrectly targeted nodes

Actual result

No visualisation, console log error

Reproduction

https://stackblitz.com/edit/github-phuuwz?file=src%2FfeedbackMachine.ts

Additional context

No response

[davidkpiano]

Very strange. I'll look into it; thank you for the report.

[josephfh]

Seems to be trying to target the machine itself on a target. This doesn't work:

      on: {
        'search.clearTerm': {
          target: '#search',
        },

This might well be an invalid way to specify a target that happens to work in XState but breaks the viz

But if I specify the initial state of the machine, it works:

      on: {
        'search.clearTerm': {
          target: '#search.starting',
        },