Skip to content

Milestones

List view

  • An early access version is getting built as this is a solution my job needs to move forward on a project. We will start this by pushing code to NPM that generates zod schemas and typescript interfaces with accurate property names, but will run into certain files that are missing or the use of any / z.any. With the early access release of v1.0.0, we can safely assume that the type names will not change, and that all making it into release should have the same properties generated as those in the Prisma client, and future improvements should expose more of the ModelAction list with greater type safety accuracy, which linting on the client side will fix. The goal for the v1.0.0 release will be a 100% matching of the prisma client, safely handling cases like circular dependency and type accuracy to be 1:1 with other production solutions, and a more verbose testing suite encompassing many combinations of ESM / Node / Prisma v5 / v6, and proper developer support for continued issue solving in post release. The goal is that once this project is released, version safety can ensure it will live long past its maintenance dates, with only SDK updates matching prisma / zod dependencies to support new versions. While the current scope of work seems limited (given the April 2025 v1 release target), we will follow the philosophy of pushing out in terms of a more secure product. Edge cases will only be found with community testing, so early access support is very much appreciated it. I am confident enough in the viability of the early access in limited releases in a production environment, but a v1.0.0 will require a much more thorough dive.

    Overdue by 1 year(s)
    Due by April 1, 2025
    1/18 issues closed