You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat!: move deleted filter to top-level query argument (#479)
* feat!: move deleted filter to top-level query argument
Soft-deleted rows are no longer part of Where inputs. List, aggregate,
singular, and reverse-relation queries on deletable entities take
`deleted: Boolean = false` instead. Skip the cascade-deletion OR in
permission EXISTS when the query does not include deleted rows.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(release): use conventionalcommits preset for commit analyzer
The angular preset does not parse feat! breaking-change notation, so
semantic-release skipped the commit on next. Align commit-analyzer with
release-notes-generator and add an explicit breaking release rule.
Co-authored-by: Cursor <cursoragent@cursor.com>
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Copy file name to clipboardExpand all lines: docs/docs/10-migration-guides.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,32 @@
1
1
# Migration Guides
2
2
3
+
## Upgrading to the next major version
4
+
5
+
### `deleted` is a top-level argument, not a `where` filter
6
+
7
+
The `deleted` field is no longer part of the auto-generated `Where` input. Instead, queries that operate on deletable entities expose a top-level `deleted: Boolean = false` argument. This applies to plural list queries, aggregate queries, singular `entity(where: …)` queries and reverse-relation list fields.
8
+
9
+
Semantics of the new argument:
10
+
11
+
- omitted or `deleted: false` (default): only non-deleted entries.
12
+
-`deleted: true`: only deleted entries (requires `DELETE` permission).
13
+
-`deleted: null`: both deleted and non-deleted entries (requires `DELETE` permission).
Permission `WHERE` rules can no longer filter on `deleted` via the generated permission `Where` types. The hard-coded `deleted = false` join used by permission chains is unchanged.
0 commit comments