@dforge-core/metadata 0.0.11 → 0.0.13

package/CHANGELOG.md

@@ -5,6 +5,55 @@ 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
+
+- **`schemas/entity.schema.json` — `flags` and `isNullable` now describe what they
+  actually do.** Both are re-vendored from `docs/schemas`; the change is to their
+  `description` text only. No constraint moved, so nothing that validated before
+  validates differently now — but these strings are what an editor shows on hover,
+  and both were misleading after `M` became load-bearing:
+  - `flags` — records that `M` is resolved into `isNullable: false` at install (so it
+    makes the column `NOT NULL`), that it is inert on virtual (`R`/`S`/`F`) and identity
+    columns, and that declaring it alongside `"isNullable": true` is rejected at pack
+    time. Previously it read only "M=Mandatory", which was true of the flag's name and
+    of nothing else — the flag was inert platform-wide until this release's server change.
+  - `isNullable` — records that omitting it means `true` (nullable), that only an
+    explicit `false` (or `M`, which resolves to it) makes a column `NOT NULL`, and that
+    adding it to a column existing tenant rows leave empty aborts the upgrade. The
+    previous text ("Whether the column allows NULL values") said nothing about the
+    default, which is the thing authors get wrong.
+
+Both correspond to the platform-side change that made an upgrade reconcile column
+nullability in both directions; see `docs/CHANGELOG.md` in `dForge-core`.
+
+## [0.0.11] — 2026-07-30
+
+Version-only republish; no content change from `0.0.10`.
+
 ## [0.0.10] — 2026-07-24
 
 ### Added