Skip to content

armgit / spree

Public Imported from GitHub
0

Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.

Record the seeded-report deletion gap as an open question

Damian Legawiec1158fa3ebc4a
diff --git a/docs/plans/6.0-analytics-semantic-layer.md b/docs/plans/6.0-analytics-semantic-layer.md
index 45a6ada8e0..14f3314ce1 100644
--- a/docs/plans/6.0-analytics-semantic-layer.md
+++ b/docs/plans/6.0-analytics-semantic-layer.md
@@ -258,6 +258,7 @@ Legacy surfaces: `Spree::Admin::AnalyticsConcern` untouched (legacy admin is mai
- **Store timezone changes** restate historical day buckets in the facts adapter — accept + document, or version the timezone per row?
- **Seller-scoped saved reports**: how store-wide saved reports appear in the seller panel once the seller forced scope lands (visibility itself is decided — Decision 12).
- **Checks/alerts** (Blazer-style scheduled saved-report thresholds → email/webhook): follow-up plan or a rider on the facts-adapter work?
+- **Deleting a seeded report**: `Seeds::SavedReports` skips by name, so a built-in report a merchant deletes returns on the next `db:seed`. A persisted seed key (or a tombstone) would let the seed tell "never created" from "deliberately removed" — it needs a column and an upgrade path for stores already seeded, so it is deferred rather than patched into the seeding loop.
- **Operations "state metrics"**: the operations card stays a bespoke point-in-time endpoint on this branch (decided — see Implementation Path); whether time-less "state metrics" ever join the registry is deferred until a second consumer wants them.
## References