Purpose
Seed Studio generates deterministic Firestore seed data from schemas/templates, stores seed snapshots, and compares generated snapshots with current project data for drift.
Flow
- Select target project/database.
- Define or choose a schema/template.
- Configure deterministic seed options.
- Generate preview data.
- Review snapshot output and logs.
- Apply the seed to Firestore with confirmation.
- Later, compare original snapshot values against current project data for drift.
Outputs
TABLE: generated records, snapshot rows, or drift rowsJSON: seed template, generated payloads, snapshots, and drift detailsLOGS: generation, validation, apply, and readback logs
Snapshot and Drift
Seed snapshots record generated values so teams can compare original fixture data with current Firestore documents. Drift output should identify unchanged, changed, missing, and extra fields/documents where the service can classify them.
Use snapshots as review evidence, not just generated fixtures. A snapshot should make the target collection paths, deterministic seed options, generated document IDs, and expected field values visible before any apply operation begins.
Drift comparison is useful after manual testing or shared emulator sessions. It helps identify which records still match the seed, which were edited during the test, and which expected documents are missing from the current project.
Safety
- Seed apply is a Firestore write and is Pro-gated.
- Template file persistence is Pro-gated.
- Production seed apply requires explicit confirmation.
- Apply operations should be task-backed and expose overwrite behavior.
Source Anchors
Sources/FirestructApp/Features/SeedStudio/UI/SeedStudioView.swiftSources/FirestructApp/Features/SeedStudio/Services/AppModel+SeedStudioActions.swiftSources/FirestructApp/Features/SeedStudio/Services/AppModel+SeedStudioPersistenceAndGeneration.swiftSources/FirestructCore/SeedStudioService.swiftSources/FirestructCore/SeedStudioService+GenerationUtilities.swift