invalid graphml import path is not hardened (can crash or fail without proper feedback) #373
Description
Import path for GraphML is brittle on malformed files. If XML is invalid or partially broken, parser path can blow up and we don’t always surface a clean, actionable error to the user.
This should be defensive: parser should reject cleanly, import handler should catch and show a proper “invalid graphml” message every time.
Repro
-
take any .graphml
-
break XML intentionally (missing closing tag etc.)
-
import it
-
watch behavior / console
what expected:
graceful failure + clear error shown to user
actual:
runtime failure / inconsistent behavior, weak error handling