Skip to main content

Exporting

DependencyAtlas has more than one export path because “graph data” can mean different things depending on your goal.

Two Main Export Kinds​

  1. Backend snapshot persistence
  2. Frontend graph export

They solve different problems and should not be confused.

Snapshot Persistence​

Snapshots are backend analysis artifacts.

They preserve:

  • canonical nodes
  • canonical edges
  • diagnostics

They do not preserve frontend layout or viewport state.

Snapshot persistence is useful for backend tooling and debugging the analysis pipeline.

Frontend JSON Export​

Frontend JSON export preserves the current exploration state, including:

  • active semantic filters
  • visible nodes and edges
  • query-context metadata such as node_appearance
  • render/layout state

This is the right export when you want to share or inspect exactly what the explorer is showing.

Draw.io Export​

Draw.io export is for communication and diagram editing rather than backend debugging.

Use it when:

  • you want to annotate a graph manually
  • you want to present a graph in a document or discussion
  • the visual arrangement matters more than the raw query payload

Which Export To Use​

Choose snapshot persistence when the consumer is analysis tooling.

Choose frontend JSON export when the consumer is another human or frontend-side debugging workflow.

Choose draw.io when the consumer is a diagramming or presentation workflow.

Practical Rule​

If you need canonical analysis data, use snapshots.
If you need “what I am seeing right now in the explorer”, use frontend export.