{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":608358512,"defaultBranch":"main","name":"prisma-soft-delete-middleware","ownerLogin":"olivierwilkinson","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2023-03-01T21:16:34.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/15321261?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1705312247.0","currentOid":""},"activityList":{"items":[{"before":"d1f62bcc88e496ee5974bf961999b2bef76d70ba","after":"04ddd6ce28b771a27069ec9bf59d99bb552425a3","ref":"refs/heads/main","pushedAt":"2024-01-15T09:48:11.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: including models in delete queries (#19)\n\nThe delete middleware does not spread args when handling a top level delete, this means that includes (and selects etc) are not found in the final params for the query.\r\n\r\nSpread args in the top level case for delete.\r\n\r\n---------\r\n\r\nCo-authored-by: Ivatra \r\nCo-authored-by: Olivier Wilkinson ","shortMessageHtmlLink":"fix: including models in delete queries (#19)"}},{"before":"6f1fb41b74774147a84cdf64c7cf86693e43e960","after":null,"ref":"refs/heads/ivatra/main","pushedAt":"2024-01-15T09:21:00.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"}},{"before":null,"after":"6f1fb41b74774147a84cdf64c7cf86693e43e960","ref":"refs/heads/ivatra/main","pushedAt":"2024-01-15T09:20:38.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: adjust spreading of args in delete params","shortMessageHtmlLink":"fix: adjust spreading of args in delete params"}},{"before":"76f54be9262fd90dc00a4086ba26d158a97f6e0a","after":"d1f62bcc88e496ee5974bf961999b2bef76d70ba","ref":"refs/heads/main","pushedAt":"2024-01-13T18:38:10.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"feat: support truthy values for deleted records (#16)\n\nCurrently, the createValue function must return a falsy value if the record is not deleted. Change the result filtering helpers so that we can define createValue functions that have a truthy value, such as Date(0), for when the record is not deleted. It should also now be theoretically possible to use a falsy value for when a record is deleted but that does not have test coverage.\r\n\r\nUpdate resultFiltering helpers to use lodash isEqual to compare values\r\nfrom createValue function. Lodash isEqual does Date comparison in a way\r\nthat works for `new Date(0) === new Date(0)`.\r\n\r\nUpdate README with explanation of new behaviour of createValue.\r\n\r\nUpdate nestedReads tests to use Date(0) as the value for non-deleted\r\nrecords, ensuring we have test coverage for that behaviour.\r\n\r\n---------\r\n\r\nCo-authored-by: misterapp \r\nCo-authored-by: Olivier ","shortMessageHtmlLink":"feat: support truthy values for deleted records (#16)"}},{"before":"8afd8b8f2b1e24577c90e48d7b452a0f8e906c8c","after":null,"ref":"refs/heads/misterapp/main","pushedAt":"2024-01-13T18:16:24.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"}},{"before":null,"after":"8afd8b8f2b1e24577c90e48d7b452a0f8e906c8c","ref":"refs/heads/misterapp/main","pushedAt":"2024-01-13T18:15:30.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: use lodash.isEqual for date value comparison\n\nUpdate resultFiltering helpers to use lodash isEqual to compare values\nfrom createValue function. Lodash isEqual does Date comparison in a way\nthat works for `new Date(0) === new Date(0)`.\n\nUpdate README with explanation of new behaviour of createValue.\n\nUpdate nestedReads tests to use Date(0) as the value for non-deleted\nrecords, ensuring we have test coverage for that behaviour.","shortMessageHtmlLink":"fix: use lodash.isEqual for date value comparison"}},{"before":"a33c1b0f3c6f5b2d4fd4922b6f490a8d71abd9f5","after":null,"ref":"refs/heads/refactor-handling-of-selects","pushedAt":"2024-01-13T16:53:40.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"}},{"before":"4f3e51c75b3eb7146c8a6160410b4a30a0e526ae","after":"76f54be9262fd90dc00a4086ba26d158a97f6e0a","ref":"refs/heads/main","pushedAt":"2024-01-13T16:53:37.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"perf: filter toMany select relations with where\n\nRather than filtering results when selecting a toMany relation ensure\nthat the relation is filtered using a modified where object in the\nquery.\n\nThis was previously difficult due to the nature of the select action:\nit was impossible to distinguish between an include.select and a\nrelational select action.\n\nUpgrading to v4 of prisma-nested-middleware removes the include.select\nvariant of the select action, allowing this library to remove the logic\nthat deferred select actions within an include to the parent action.\nThat logic that deferred to the parent also prevented always modifying\nthe select action to use the where strategy.","shortMessageHtmlLink":"perf: filter toMany select relations with where"}},{"before":null,"after":"a33c1b0f3c6f5b2d4fd4922b6f490a8d71abd9f5","ref":"refs/heads/refactor-handling-of-selects","pushedAt":"2024-01-13T16:43:45.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"perf: filter toMany select relations with where\n\nRather than filtering results when selecting a toMany relation ensure\nthat the relation is filtered using a modified where object in the\nquery.\n\nThis was previously difficult due to the nature of the select action:\nit was impossible to distinguish between an include.select and a\nrelational select action.\n\nUpgrading to v4 of prisma-nested-middleware removes the include.select\nvariant of the select action, allowing this library to remove the logic\nthat deferred select actions within an include to the parent action.\nThat logic that deferred to the parent also prevented always modifying\nthe select action to use the where strategy.","shortMessageHtmlLink":"perf: filter toMany select relations with where"}},{"before":"c5b143efb82304c3eef88a5f41b17b6bd7e2c31a","after":"4f3e51c75b3eb7146c8a6160410b4a30a0e526ae","ref":"refs/heads/main","pushedAt":"2023-11-04T15:21:18.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"docs(README): middleware deprecation and extension\n\nAdd a section to explain that there is an extension alternative since\nPrisma middleware has been deprecated. Also clarify that this library\nwill still be maintained as long as Prisma maintains middleware.","shortMessageHtmlLink":"docs(README): middleware deprecation and extension"}},{"before":"71616202dce2f832518f97b7f4f3c082de39172c","after":null,"ref":"refs/heads/support-find-first-or-throw","pushedAt":"2023-10-29T15:06:39.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"}},{"before":"8fc3652f350042c59f064fe4150b349840ffba0b","after":"c5b143efb82304c3eef88a5f41b17b6bd7e2c31a","ref":"refs/heads/main","pushedAt":"2023-10-29T15:06:34.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"build: fix release with Prisma v5\n\nPrisma v5 only supports Node version 16 or later. Update the github\nactions Release job to use Node 16.","shortMessageHtmlLink":"build: fix release with Prisma v5"}},{"before":"c535135c2dec2d1fbecb349bdebeec11c563d37b","after":"71616202dce2f832518f97b7f4f3c082de39172c","ref":"refs/heads/support-find-first-or-throw","pushedAt":"2023-10-29T15:01:30.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"build: fix release with Prisma v5\n\nPrisma v5 only supports Node version 16 or later. Update the github\nactions Release job to use Node 16.","shortMessageHtmlLink":"build: fix release with Prisma v5"}},{"before":"faa1f8f97d15f8b0d34e2a0b973a5c26ae691289","after":"c535135c2dec2d1fbecb349bdebeec11c563d37b","ref":"refs/heads/support-find-first-or-throw","pushedAt":"2023-10-29T14:54:41.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"feat: support Prisma v5 find*OrThrow actions (#14)\n\nPrisma v5 moved away from configuring whether to throw or not when a\nfindOne does not have a result, instead opting to encourage using\nfindFirstOrThrow and findUniqueOrThrow methods on the client.\n\nThe removal of the configurable throwing behaviour meant that the\nmiddleware actions added findFirstOrThrow and findUniqueOrThrow as\noptions.\n\nUpdate the list of action middleware to handle orThrow variants and\nupdate the version of Prisma we test against to the latest v5 version.\n\nAlso refactor the findUnique middleware to precalculate uniqueFields\nand uniqueIndexFields at the top of actionMiddleware, this avoids having\nto recalculate when handling each findUnique or findUniqueOrThrow\noperation. At the same time it makes sense to refactor the logic for\nwhether to pass the params through in the findUnique case and when to\nthrow into separate helpers, this makes it easier to understand when\nparams are passed through vs when we should throw.","shortMessageHtmlLink":"feat: support Prisma v5 find*OrThrow actions (#14)"}},{"before":"5da17a953f05ed4c3bf8d4aaaf9168e91c51d0be","after":"faa1f8f97d15f8b0d34e2a0b973a5c26ae691289","ref":"refs/heads/support-find-first-or-throw","pushedAt":"2023-10-29T14:34:15.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"feat: support Prisma v5 find*OrThrow actions (#14)\n\nPrisma v5 moved away from configuring whether to throw or not when a\nfindOne does not have a result, instead opting to encourage using\nfindFirstOrThrow and findUniqueOrThrow methods on the client.\n\nThe removal of the configurable throwing behaviour meant that the\nmiddleware actions added findFirstOrThrow and findUniqueOrThrow as\noptions.\n\nUpdate the list of action middleware to handle orThrow variants and\nupdate the version of Prisma we test against to the latest v5 version.\n\nAlso refactor the findUnique to precalculate the uniqueFields and\nuniqueIndexFields at the top of actionMiddleware, this avoids having to\nrecalculate when handling each findUnique or findUniqueOrThrow\noperation; this has an added benefit of simplifying the middlware logic.","shortMessageHtmlLink":"feat: support Prisma v5 find*OrThrow actions (#14)"}},{"before":null,"after":"5da17a953f05ed4c3bf8d4aaaf9168e91c51d0be","ref":"refs/heads/support-find-first-or-throw","pushedAt":"2023-10-29T14:31:11.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"feat: support Prisma v5 find*OrThrow actions (#14)\n\nPrisma v5 moved away from configuring whether to throw or not when a\nfindOne does not have a result, instead opting to encourage using\nfindFirstOrThrow and findUniqueOrThrow methods on the client.\n\nThe removal of the configurable throwing behaviour meant that the\nmiddleware actions added findFirstOrThrow and findUniqueOrThrow as\noptions.\n\nUpdate the list of action middleware to handle orThrow variants and\nupdate the version of Prisma we test against to the latest v5 version.","shortMessageHtmlLink":"feat: support Prisma v5 find*OrThrow actions (#14)"}},{"before":"d7e41a160bbcbbf3bd1942c96d88979cc8c1498a","after":"8fc3652f350042c59f064fe4150b349840ffba0b","ref":"refs/heads/main","pushedAt":"2023-06-05T00:31:35.498Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: findUnique with compound unique index where\n\nWhen using a findUnique query with a compound unique index field in the\nwhere object, such as \"name_email\" for the User model, the action is\nchanged to findFirst which does not support that where field.\n\nThrow when encountering compound unique index fields in the findUnique\nwhere object by default since using findUnique we cannot exclude\nsoft deleted models. Add a \"allowCompoundUniqueIndexWhere\" field to the\nmodel config to allow users to override the default behaviour. When the\ndefault behaviour is overridden don't switch the action type to\nfindFirst, but also don't exclude soft deleted models.\n\nThis is not a breaking change since all queries that currently use\ncompound index where fields throw anyways, so throwing at that time does\nnot cause a change in behaviour, only in the error message.","shortMessageHtmlLink":"fix: findUnique with compound unique index where"}},{"before":"c9c2667e364404fcfd74290b97a3f69755d349b6","after":"7b73d98e357f8c3eb0c69e8262eb6d9aee722e57","ref":"refs/heads/fix-compound-unique-index-queries-failing","pushedAt":"2023-06-04T23:38:17.040Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: findUnique with compound unique index where\n\nWhen using a findUnique query with a compound unique index field in the\nwhere object, such as \"name_email\" for the User model, the action is\nchanged to findFirst which does not support that where field.\n\nThrow when encountering compound unique index fields in the findUnique\nwhere object by default since using findUnique we cannot exclude\nsoft deleted models. Add a \"allowCompoundUniqueIndexWhere\" field to the\nmodel config to allow users to override the default behaviour. When the\ndefault behaviour is overridden don't switch the action type to\nfindFirst, but also don't exclude soft deleted models.\n\nThis is not a breaking change since all queries that currently use\ncompound index where fields throw anyways, so throwing at that time does\nnot cause a change in behaviour, only in the error message.","shortMessageHtmlLink":"fix: findUnique with compound unique index where"}},{"before":"7a095df9a48a14ed51bf1c8fb484613d967756e8","after":null,"ref":"refs/heads/fix-invalid-find-unique-where","pushedAt":"2023-06-04T23:37:02.500Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"}},{"before":"35f2bc75b3b1af8ee44e93447410da258ab1a9fd","after":"d7e41a160bbcbbf3bd1942c96d88979cc8c1498a","ref":"refs/heads/main","pushedAt":"2023-06-04T23:36:59.086Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: returning models for invalid findUnique where\n\nCloses #4\n\nWhen a findUnique query is passed an invalid where object, for example\none with `id: undefined`, the deleted field is still added to the where\nand the action is converted to findFirst. This causes a model to be\nincorrectly returned when it should not be, instead the query should\nthrow due to Prisma validation.\n\nUse the DMMF to validate that the where object has at least one unique\nfield that is not undefined before changing the action type to\nfindFirst.","shortMessageHtmlLink":"fix: returning models for invalid findUnique where"}},{"before":null,"after":"c9c2667e364404fcfd74290b97a3f69755d349b6","ref":"refs/heads/fix-compound-unique-index-queries-failing","pushedAt":"2023-06-04T20:30:45.629Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: findUnique with compound unique index where\n\nWhen using a findUnique query with a compound unique index field in the\nwhere object, such as \"name_email\" for the User model, the action is\nchanged to findFirst which does not support that where field.\n\nThrow when encountering compound unique index fields in the findUnique\nwhere object by default since using findUnique we cannot exclude\nsoft deleted models. Add a \"allowCompoundUniqueIndexWhere\" field to the\nmodel config to allow users to override the default behaviour. When the\ndefault behaviour is overridden don't switch the action type to\nfindFirst, but also don't exclude soft deleted models.\n\nThis is not a breaking change since all queries that currently use\ncompound index where fields throw anyways, so throwing at that time does\nnot cause a change in behaviour, only in the error message.","shortMessageHtmlLink":"fix: findUnique with compound unique index where"}},{"before":null,"after":"7a095df9a48a14ed51bf1c8fb484613d967756e8","ref":"refs/heads/fix-invalid-find-unique-where","pushedAt":"2023-06-04T20:30:27.656Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: returning models for invalid findUnique where\n\nCloses #4\n\nWhen a findUnique query is passed an invalid where object, for example\none with `id: undefined`, the deleted field is still added to the where\nand the action is converted to findFirst. This causes a model to be\nincorrectly returned when it should not be, instead the query should\nthrow due to Prisma validation.\n\nUse the DMMF to validate that the where object has at least one unique\nfield that is not undefined before changing the action type to\nfindFirst.","shortMessageHtmlLink":"fix: returning models for invalid findUnique where"}},{"before":"82561f6ec41329feb8ea44c0e5613ab5ac12adeb","after":"35f2bc75b3b1af8ee44e93447410da258ab1a9fd","ref":"refs/heads/main","pushedAt":"2023-05-26T19:32:31.819Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"feat: add support for groupBy queries (#7)\n\nUpdate version of prisma-nested-middleware to v3.0.3 so 'groupBy' is included as an option for NestedAction.","shortMessageHtmlLink":"feat: add support for groupBy queries (#7)"}},{"before":"3770470cdb5d2c148f14cb492b6b1675bba40351","after":null,"ref":"refs/heads/fix-queries-with-missing-args","pushedAt":"2023-04-18T17:37:37.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"}},{"before":"e02839cf09e629bb6c2a0d90e16d04acac4bb869","after":"82561f6ec41329feb8ea44c0e5613ab5ac12adeb","ref":"refs/heads/main","pushedAt":"2023-04-18T17:37:30.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: queries without args or where\n\nCurrently there are cases where it is assumed that the args object is\ndefined, and also the where object within. This is not always correct,\nfor example findMany can be used without args or a where.\n\nUpdate action middleware to ensure operations that can being used\nwithout args or a where object are supported.\n\nAdditionally, we are assuming the user is passing valid arguments all\nthe time, however there are cases where it would be better to allow\nPrisma to throw an error rather than trying to modify the params.\n\nPass root delete operations with no where, findUnique operations with no\nwhere and updateMany operations with no args through to Prisma to throw\na useful error.","shortMessageHtmlLink":"fix: queries without args or where"}},{"before":"0472fcc9d9612ef92cf6cb74dcbfb1184b1e0702","after":"3770470cdb5d2c148f14cb492b6b1675bba40351","ref":"refs/heads/fix-queries-with-missing-args","pushedAt":"2023-04-18T17:28:41.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: queries without args or where\n\nCurrently there are cases where it is assumed that the args object is\ndefined, and also the where object within. This is not always correct,\nfor example findMany can be used without args or a where.\n\nUpdate action middleware to ensure operations that can being used\nwithout args or a where object are supported.\n\nAdditionally, we are assuming the user is passing valid arguments all\nthe time, however there are cases where it would be better to allow\nPrisma to throw an error rather than trying to modify the params.\n\nPass root delete operations with no where, findUnique operations with no\nwhere and updateMany operations with no args through to Prisma to throw\na useful error.","shortMessageHtmlLink":"fix: queries without args or where"}},{"before":"6fbf6c012ba596c92a97311fa9164ce1b86aa1b8","after":"0472fcc9d9612ef92cf6cb74dcbfb1184b1e0702","ref":"refs/heads/fix-queries-with-missing-args","pushedAt":"2023-04-18T17:26:23.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: queries without args or where\n\nCurrently there are cases where it is assumed that the args object is\ndefined, and also the where object within. This is not always correct,\nfor example findMany can be used without args or a where.\n\nUpdate action middleware to ensure operations that can being used\nwithout args or a where object are supported.\n\nAdditionally, we are assuming the user is passing valid arguments all\nthe time, however there are cases where it would be better to allow\nPrisma to throw an error rather than trying to modify the params.\n\nPass root delete operations with no where, findUnique operations with no\nwhere and updateMany operations with no args through to Prisma to throw\na useful error.","shortMessageHtmlLink":"fix: queries without args or where"}},{"before":"2bf7c05cf298b7d28d550b79c62fd5f8b36a802b","after":"6fbf6c012ba596c92a97311fa9164ce1b86aa1b8","ref":"refs/heads/fix-queries-with-missing-args","pushedAt":"2023-04-18T17:21:49.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: queries without args or where\n\nCurrently there are cases where it is assumed that the args object is\ndefined, and also the where object within. This is not always correct,\nfor example findMany can be used without args or a where.\n\nUpdate action middleware to ensure operations that can being used\nwithout args or a where object are supported.\n\nAdditionally, we are assuming the user is passing valid arguments all\nthe time, however there are cases where it would be better to allow\nPrisma to throw an error rather than trying to modify the params.\n\nPass root delete operations with no where and updateMany operations\nwith no args through to Prisma to throw a useful error.","shortMessageHtmlLink":"fix: queries without args or where"}},{"before":null,"after":"2bf7c05cf298b7d28d550b79c62fd5f8b36a802b","ref":"refs/heads/fix-queries-with-missing-args","pushedAt":"2023-04-18T17:19:34.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"fix: queries without args or where\n\nCurrently there are cases where it is assumed that the args object is\ndefined, and also the where object within. This is not always correct,\nfor example findMany can be used without args or a where.\n\nUpdate action middleware to ensure operations that can being used\nwithout args or a where object are supported.\n\nAdditionally, we are assuming the user is passing valid arguments all\nthe time, however there are cases where it would be better to allow\nPrisma to throw an error rather than trying to modify the params.\n\nPass root delete operations with no where and updateMany operations\nwith no args through to Prisma to throw a useful error.","shortMessageHtmlLink":"fix: queries without args or where"}},{"before":"94ba103ecb8a3a2f2d812a3675b48bcd602d82ca","after":"e02839cf09e629bb6c2a0d90e16d04acac4bb869","ref":"refs/heads/main","pushedAt":"2023-03-30T22:55:59.329Z","pushType":"push","commitsCount":1,"pusher":{"login":"olivierwilkinson","name":"Olivier","path":"/olivierwilkinson","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15321261?s=80&v=4"},"commit":{"message":"docs: improve behaviour section summary","shortMessageHtmlLink":"docs: improve behaviour section summary"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wMS0xNVQwOTo0ODoxMS4wMDAwMDBazwAAAAPf4cHK","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wMS0xNVQwOTo0ODoxMS4wMDAwMDBazwAAAAPf4cHK","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wMy0zMFQyMjo1NTo1OS4zMjk4NjlazwAAAAMPDlnv"}},"title":"Activity ยท olivierwilkinson/prisma-soft-delete-middleware"}