Update dependency typegraphql-prisma to ^0.26.0 #100

renovate · 2023-04-01T08:00:36Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typegraphql-prisma	`^0.23.5` -> `^0.26.0`

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

Release Notes

MichalLytek/typegraphql-prisma

`v0.26.0`: 0.26.0

Compare Source

Changelog

Supported Prisma version has been bumped to ^4.15.0 💪
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.
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

`v0.25.1`: 0.25.1

Compare Source

Changelog

Supported Prisma version has been bumped to v4.14.0 💪
No changes in DMMF, so all should upgrade without any issues.
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 👍
Read about the future of typegraphql-prisma 👀

`v0.25.0`: 0.25.0

Compare Source

Changelog

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! 📻

`v0.24.7`: 0.24.7

Compare Source

Changelog

Supported Prisma version has been bumped to v4.13.0 💪
No changes in DMMF, so all should upgrade without any issues.
Stay tuned for more changes - they are in progress 📻

`v0.24.6`: 0.24.6

Compare Source

Changelog

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

`v0.24.5`: 0.24.5

Compare Source

Changelog

Supported Prisma version has been bumped to v4.12.0 💪
No changes in DMMF, so all should upgrade without any issues.
No more changes, this week was mostly about debugging reported issues and reporting issues upstream on Prisma repo 👀

`v0.24.4`: 0.24.4

Compare Source

Changelog

It is now possible to configure generator to always omit some field in input or output types for all models (#356).

Some fields like createdAt or updatedAt are being frequently omitted from input types, which is cumbersome to manually maintain in schema.prisma file for all the models. Hence there are now two new generator options that allows to omit by default some fields - omitInputFieldsByDefault and omitOutputFieldsByDefault, e.g.:
```
generator typegraphql {
  provider                  = "typegraphql-prisma"
  omitInputFieldsByDefault  = "createdAt,updatedAt"
  omitOutputFieldsByDefault = "password"
}
```
You can find more info about this feature in the docs:
https://prisma.typegraphql.com/docs/advanced/hiding-field#omit-fields-by-default

`v0.24.3`: 0.24.3

Compare Source

Changelog

Due to a bug in a Prisma Client (https://github.com/prisma/prisma/issues/18326), there was an issue with getting relations during findMany queries (#367).
This has been fixed and now the queries should work without any issues 💪
You might expect some changes in generated resolvers because of patching small issue with redundant type infos - using _returns which now is _type: @TypeGraphQL.Args(_type => AggregateCategoryArgs) args: AggregateCategoryArgs

`v0.24.2`: 0.24.2

Compare Source

Changelog

Supported Prisma version has been bumped to v4.11.0 💪
Because of small changes in DMMF, you may expect changes in the order of fields in generated code:

@&#8203;TypeGraphQL.InputType("CommentWhereInput", {
  isAbstract: true
})
export class CommentWhereInput {
  // ...

- @&#8203;TypeGraphQL.Field(_type => PostRelationFilter, {
-   nullable: true
- })
- post?: PostRelationFilter | undefined;

  @&#8203;TypeGraphQL.Field(_type => StringFilter, {
    nullable: true
  })
  comment?: StringFilter | undefined;

+ @&#8203;TypeGraphQL.Field(_type => PostRelationFilter, {
+  nullable: true
+ })
+ post?: PostRelationFilter | undefined;
}

However, it won't affect any schema capabilities, so you can safely upgrade 👌

`v0.24.1`: 0.24.1

Compare Source

Changelog

This release is a hotfix for a bug introduced in v0.24.0 and reported in #361.
Now the _all property should be optional for both resolvers and types/models 🙌

`v0.24.0`: 0.24.0

Compare Source

Changelog

Support for overriding _all property decorators in enhance maps has been added 🚀

Now you can use the function variant to override decorators declared for all resolver methods:

applyResolversEnhanceMap({
  Story: {
    _all: [Authorized(Role.ADMIN, Role.MEMBER)],
    createStory: () => [Authorized(Role.SUPER_ADMIN)], // require higher role
    story: () => [], // make it public by returning no `@Authorized` decorators
  },
});

And even combine the "all" decorators with the ones for selected method:

applyResolversEnhanceMap({
  Client: {
    _all: [Extensions({ logMessage: "Fun zone" }), Authorized()],
    deleteClient:
      // ignore log message extension
      ([_logExtension, auth]) => [
        // provide own message
        Extensions({ logMessage: "Danger zone" }),
        // passthrough the "all" auth decorator
        auth,
      ],
  },
});

This feature works for all enhance maps - resolvers, relation resolvers, models, outputs and input types, e.g.:

applyModelsEnhanceMap({
  User: {
    fields: {
      // all fields are protected against unauthorized access
      _all: [Authorized()],
      // this field has additional decorators to apply
      password: [
        Extensions({ logMessage: "Danger zone", logLevel: LogLevel.WARN }),
      ],
      // this field is public, no `@Authorized` decorator returned
      id: allDecorators => [],
    },
  },
});

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate · 2023-04-01T08:00:37Z

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/graphql-scalars
npm ERR!   graphql-scalars@"^1.20.1" from the root project
npm ERR!   graphql-scalars@"1.20.1" from @omnigraph/[email protected]
npm ERR!   node_modules/@omnigraph/json-schema
npm ERR!     @omnigraph/json-schema@"0.38.8" from @omnigraph/[email protected]
npm ERR!     node_modules/@omnigraph/openapi
npm ERR!       @omnigraph/openapi@"0.19.9" from @graphql-mesh/[email protected]
npm ERR!       node_modules/@graphql-mesh/openapi
npm ERR!         @graphql-mesh/openapi@"^0.35.9" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! typegraphql-prisma@"^0.26.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/graphql-scalars
npm ERR!   peer graphql-scalars@"^1.22.2" from [email protected]
npm ERR!   node_modules/typegraphql-prisma
npm ERR!     typegraphql-prisma@"^0.26.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/43a7a3/362a57/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/43a7a3/362a57/cache/others/npm/_logs/2023-06-22T05_31_33_671Z-debug-0.log

netlify · 2023-04-01T08:00:42Z

❌ Deploy Preview for alternatedemo failed.

Name	Link
🔨 Latest commit	`5ef5257`
🔍 Latest deploy log	https://app.netlify.com/sites/alternatedemo/deploys/6427e4a61708390008806a99

Sebastian Hilton added 2 commits March 30, 2023 16:42

updated the UI to match Collaborrate's goal, features, and color scheme

35d3215

updated the UI to match Collaborrate's goal, features, and color scheme

c90faeb

renovate bot force-pushed the renovate/typegraphql-prisma-0.x branch from 5ef5257 to dccbd7d Compare April 26, 2023 12:39

renovate bot changed the title ~~Update dependency typegraphql-prisma to ^0.24.0~~ Update dependency typegraphql-prisma to ^0.25.0 Apr 26, 2023

Update dependency typegraphql-prisma to ^0.26.0

9652a77

renovate bot changed the title ~~Update dependency typegraphql-prisma to ^0.25.0~~ Update dependency typegraphql-prisma to ^0.26.0 Jun 22, 2023

renovate bot force-pushed the renovate/typegraphql-prisma-0.x branch from dccbd7d to 9652a77 Compare June 22, 2023 05:31

bastianhilton closed this Jul 13, 2023

bastianhilton force-pushed the main branch from c90faeb to 6960bbe Compare July 13, 2023 19:09

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency typegraphql-prisma to ^0.26.0 #100

Update dependency typegraphql-prisma to ^0.26.0 #100

renovate bot commented Apr 1, 2023 •

edited

Loading

renovate bot commented Apr 1, 2023 •

edited

Loading

netlify bot commented Apr 1, 2023 •

edited

Loading

Update dependency typegraphql-prisma to ^0.26.0 #100

Update dependency typegraphql-prisma to ^0.26.0 #100

Conversation

renovate bot commented Apr 1, 2023 • edited Loading

⚠ Dependency Lookup Warnings ⚠

Release Notes

v0.26.0: 0.26.0

Changelog

v0.25.1: 0.25.1

Changelog

v0.25.0: 0.25.0

Changelog

v0.24.7: 0.24.7

Changelog

v0.24.6: 0.24.6

Changelog

v0.24.5: 0.24.5

Changelog

v0.24.4: 0.24.4

Changelog

v0.24.3: 0.24.3

Changelog

v0.24.2: 0.24.2

Changelog

v0.24.1: 0.24.1

Changelog

v0.24.0: 0.24.0

Changelog

Configuration

renovate bot commented Apr 1, 2023 • edited Loading

⚠ Artifact update problem

File name: package-lock.json

netlify bot commented Apr 1, 2023 • edited Loading

❌ Deploy Preview for alternatedemo failed.

renovate bot commented Apr 1, 2023 •

edited

Loading

`v0.26.0`: 0.26.0

`v0.25.1`: 0.25.1

`v0.25.0`: 0.25.0

`v0.24.7`: 0.24.7

`v0.24.6`: 0.24.6

`v0.24.5`: 0.24.5

`v0.24.4`: 0.24.4

`v0.24.3`: 0.24.3

`v0.24.2`: 0.24.2

`v0.24.1`: 0.24.1

`v0.24.0`: 0.24.0

renovate bot commented Apr 1, 2023 •

edited

Loading

netlify bot commented Apr 1, 2023 •

edited

Loading