Skip to content

Releases: MichalLytek/typegraphql-prisma

0.28.0

07 Aug 13:58
Compare
Choose a tag to compare
0.28.0 Pre-release
Pre-release

Changelog

  1. The Prisma dependency version has been bumped to v5.18.0 💪

  2. Because of Prisma v5 recent changes, the ...OrderByWithRelationAndSearchRelevanceInput has been replaced by standard ...OrderByWithRelationInput. You can expect breaking changes in the generated schema because of that 🚨

  3. The new createManyAndReturn Prisma operation is fully supported in this release 🎉

  4. The supported Node.js version has been bumped to v20.11.1.

0.27.2

28 Feb 14:25
Compare
Choose a tag to compare
0.27.2 Pre-release
Pre-release

Changelog

  1. This release contains a revert of the change from v0.27.1.
    Due to the issues with the way how undefined class properties are initialized, ES target in tsconfig.json file has been downgraded to "es2021".

  2. It is now possible to define multiple @TypeGraphQL comment-based attributes on a single field of Prisma schema model (#400).

0.27.1

18 Oct 13:53
Compare
Choose a tag to compare
0.27.1 Pre-release
Pre-release

Changelog

  1. It has been tested that typegraphql-prisma can work with Prisma release v5.4.2 💪
    This only address backward compatibility and does not include support for any new features.
    Please refer to the installation docs warning message:
    https://prisma.typegraphql.com/docs/basics/installation#typegraphql-prisma-generator

  2. Because of Prisma v5.0 recent change, the supported Node.js version has been bumped to v16.13.0 or newer, together with ES2022 compilation target.

  3. The overhead of generated TS source code transpilation done by generator was reduced by ~50% 🚀
    All thanks to setting "skipLibCheck": true, in compilerOptions of tsconfig.json.

    Before: 7.63s
    After: 5.53s
    emitTranspiledCode = false: 2.51s

0.27.0

19 Jul 15:19
Compare
Choose a tag to compare
0.27.0 Pre-release
Pre-release

Changelog

  1. Supported Prisma version has been bumped to ^5.0.0 💪

  2. As it's a breaking change Prisma release, plenty of preview features has been promoted to stable and enabled by default, like orderByNulls, extendedWhereUnique and filteredRelationCount, so please expect breaking changes in your GraphQL API if you haven't used that features yet.

  3. Generator options like emitOnly or omitInputFieldsByDefault now supports array-based syntax, so you don't need to use the string-like arrays workaround anymore 😎
    Before:

    emitOnly = "enums,models"

    After:

    emitOnly = ["enums", "models"]

0.26.0

19 Jun 10:52
Compare
Choose a tag to compare
0.26.0 Pre-release
Pre-release

Changelog

  1. Supported Prisma version has been bumped to ^4.15.0 💪

  2. As the v2.0.0.beta-2 release of TypeGraphQL has removed the legacy isAbstract decorator option, it is now not emitted by default by the generator.

  3. A new generator option called emitIsAbstract has been introduced. It restores the old behavior of emitting isAbstract: true decorator option for @ObjectType (models, outputs) and @InputType classes.
    More info about this feature (and when to use it) can be found in the docs:
    https://prisma.typegraphql.com/docs/advanced/emit-is-abstract

0.25.1

10 May 10:16
Compare
Choose a tag to compare
0.25.1 Pre-release
Pre-release

Changelog

  1. Supported Prisma version has been bumped to v4.14.0 💪
    No changes in DMMF, so all should upgrade without any issues.

  2. The Prisma version check mechanizm has been loosened and now it uses ^ check for major version changes.
    It is more convenient for users but in some future there might occur some breaking changes as Prisma internals are not a subject for semantic versioning. Please report all the issues encountered with new Prisma version upgrade 👍

  3. Read about the future of typegraphql-prisma 👀

0.25.0

26 Apr 11:50
Compare
Choose a tag to compare
0.25.0 Pre-release
Pre-release

Changelog

  1. Support for enhancing resolvers with decorators by CRUD scope (#300) is implemented in a first phase 🚀
    Since this release, you can use _mutation and _query shorthand syntax, apart from the _all one:

    applyResolversEnhanceMap({
      Client: {
        _all: [UseMiddleware(LogMiddleware)],
        _query: [Authorized()],
        _mutation: [Authorized(Role.ADMIN)], // only admin can change the data
      },
    });

    The decorators from _mutation and _query are joined with those from _all and then passed to the selected actions enhancers 💪
    The next iteration will add support for even more granular control: _create, _read, _update and _delete. Stay tuned! 📻

0.24.7

26 Apr 10:37
Compare
Choose a tag to compare
0.24.7 Pre-release
Pre-release

Changelog

  1. Supported Prisma version has been bumped to v4.13.0 💪
    No changes in DMMF, so all should upgrade without any issues.

  2. Stay tuned for more changes - they are in progress 📻

0.24.6

12 Apr 17:13
Compare
Choose a tag to compare
0.24.6 Pre-release
Pre-release

Changelog

  1. This release brings a new generated code formatting options 🚀
    You can now use formatGeneratedCode generator option to either set code formatting using Prettier or disable it at all to save some time while generating 🎉
    More info about this feature in the docs: https://prisma.typegraphql.com/docs/basics/configuration#formatting-generated-code

0.24.5

29 Mar 14:02
Compare
Choose a tag to compare
0.24.5 Pre-release
Pre-release

Changelog

  1. Supported Prisma version has been bumped to v4.12.0 💪
    No changes in DMMF, so all should upgrade without any issues.

  2. No more changes, this week was mostly about debugging reported issues and reporting issues upstream on Prisma repo 👀