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 what happens to a report written before the metric rename

Damian Legawiec7df417706667
diff --git a/docs/plans/6.0-analytics-semantic-layer.md b/docs/plans/6.0-analytics-semantic-layer.md
index e49a2437e7..f36799dc9a 100644
--- a/docs/plans/6.0-analytics-semantic-layer.md
+++ b/docs/plans/6.0-analytics-semantic-layer.md
@@ -307,6 +307,7 @@ Legacy surfaces: `Spree::Admin::AnalyticsConcern` untouched (legacy admin is mai
## Open Questions
+- **Saved reports written against the pre-rename vocabulary** (only possible on a store seeded from this branch before 2026-09-09): the row survives, and both paths refuse it loudly — a save fails validation naming every valid metric, and running an existing row raises `UnknownMember` with the same list. Nothing rewrites them, because a rename is not always a substitution (`net_revenue` has no successor with the same meaning). If any such store exists at release, the note belongs in the upgrade guide rather than in a data task.
- **Fact currency handling**: per-currency fact rows (query one currency at a time, mirroring Live) vs converted-at-write "reporting currency" columns. Leaning per-currency rows; conversion is a display concern until merchants demand blended totals.
- **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).