[Phase 1] Implement canonical JSON, GraphML, and CSV import/export #11

New issue

Closed

opened 2026-07-25 21:53:12 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-25 21:53:12 +00:00

(Migrated from github.com)

Parent: #2
Depends on: #6, #7, #8, #10

Scope

Implement canonical Quasar graph JSON import and export.
Preserve stable IDs, types, properties, positions, viewport, metadata, and unknown extension fields.
Add GraphML import/export with explicit type preservation rules.
Add CSV node and edge import through a mapping wizard or mapping configuration.
Validate size, shape, references, and batch limits before committing imports.

Acceptance criteria

Canonical JSON round-trips losslessly.
Imports apply through one atomic graph batch.
Invalid or oversized imports fail without changing the current graph.
GraphML and CSV limitations are visible to the user.
Exported files use deterministic naming and content ordering where practical.

Parent: #2 Depends on: #6, #7, #8, #10 ## Scope - Implement canonical Quasar graph JSON import and export. - Preserve stable IDs, types, properties, positions, viewport, metadata, and unknown extension fields. - Add GraphML import/export with explicit type preservation rules. - Add CSV node and edge import through a mapping wizard or mapping configuration. - Validate size, shape, references, and batch limits before committing imports. ## Acceptance criteria - Canonical JSON round-trips losslessly. - Imports apply through one atomic graph batch. - Invalid or oversized imports fail without changing the current graph. - GraphML and CSV limitations are visible to the user. - Exported files use deterministic naming and content ordering where practical.