@dforge-core/metadata 0.0.12 → 0.0.13

package/CHANGELOG.md

@@ -5,6 +5,28 @@ All notable changes to `@dforge-core/metadata` are documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this package adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.0.13] — 2026-08-07
+
+### Changed
+
+- **Filter operators are now a closed, enumerated set.** `FilterCondition.o` and
+  `FilterGroup.g` were typed as plain `string`, and the `o` field in
+  `schemas/{data_views,reports,folders}.schema.json` had no `enum` — its description
+  listed operators that never existed (`isNull`, `isNotNull`, `neq`, `gt`, `gte`,
+  `lt`, `lte`, `like`). Modules were authored against that list; the server drops an
+  operator it can't translate, so those conditions were silently discarded at query
+  time and the query ran *wider* than written. The schemas now carry an `enum`, and
+  the TS types narrow to the new `FilterOperator` / `FilterGroupOperator` unions,
+  exported alongside the `FILTER_OPERATORS` / `FILTER_GROUP_OPERATORS` value arrays.
+
+  The real spellings for the ones most often invented: `null` / `!null` (not
+  `isNull` / `isNotNull`), `contains` or `mask` (not `like`), and
+  `!=` / `>` / `>=` / `<` / `<=` (not `neq` / `gt` / `gte` / `lt` / `lte`).
+
+  **Breaking for TypeScript consumers** that assign an arbitrary `string` to `o` or
+  `g` — those assignments now fail to compile, which is the point: dForge-core
+  rejects the same values at module install.
+
 ## [0.0.12] — 2026-08-04
 
 ### Changed