@relyio/sdk 0.9.0 → 0.10.0

package/CHANGELOG.md

@@ -1,5 +1,26 @@
 # @relyio/sdk
 
+## 0.10.0
+
+### Minor Changes
+
+- d147cb3: **A view's filters are a flat list.** `defineView`'s `filters` take `{ field, operator, value }` filters, joined by AND — the Filters the Studio's entry list takes, each shown as a chip. The group form, an `operator` with `conditions`, is gone: `ViewFilterGroup` is no longer exported, `ViewFilter` is one filter, and `defineView` throws, naming the view and the filter, if you pass a group from JavaScript. For an OR within one field, use `isAnyOf`:
+
+  ```ts
+  defineView('newsAndSport', {
+    name: 'News and sport',
+    scope: { type: 'contentType', contentType: 'post' },
+    filters: [
+      { field: 'category', operator: 'isAnyOf', value: ['news', 'sport'] },
+      { field: 'featured', operator: 'is', value: true },
+    ],
+  })
+  ```
+
+  A YAML schema's `views[].filters` are the same list, and `relyio validate` and `relyio deploy` refuse a filter group by name, at `views.<n>.filters.<n>`.
+
+  **Deploy now checks each view filter against the entries it narrows.** The field must be one the view's entries can be filtered by, and must offer the operator and take the value — so a boolean field takes `is` with `true` or `false`, not `isTrue`, and a tags field is not filtered with `includes`. A filter that does not fit is refused by name at `views.<n>.filters.<n>.field`, `.operator` or `.value`. `relyio status` refuses it too. `relyio validate` checks a view filter's shape, not this: run `relyio status` to see what deploy will say.
+
 ## 0.9.0
 
 ### Minor Changes