-
Notifications
You must be signed in to change notification settings - Fork 396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: upgrade Mercurius, Apollo, GraphQL to the latest versions #2636
Conversation
Fields with arguments are usually resolved using a separate method with the @ResolveField() annotation. Having such field generated as a required property thus proves quite cumbersome as it forces assigning a value in the result of parent @query() method. This makes fields with arguments always optional.
fix(deps): remove git conflict markers and keep latest rimraf version
Fixing pipes spec tests. Changed ApolloServerPluginInlineTraceDisabled reference to '@apollo/server/plugin/disabled'; Changed ApolloServerBase references to ApolloServer.
chore: fixing pipes and code-first spec tests and some code cleanup
You can get the latest changes from this repository check it out and pull it to fix the playground issue |
There's no "playground" issue. Current settings are intentional ant this was discussed several times in the past |
Fix/apollo context
…ents-optional fix(graphql): generate fields as optional when they contain arguments
feat(types): Type check Field defaultValue
"@nestjs/common": "8.4.7", | ||
"@nestjs/platform-fastify": "8.4.7", | ||
"@nestjs/testing": "8.4.7", | ||
"@mercuriusjs/federation": "^1.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"@mercuriusjs/federation": "^1.0.0", | |
"@mercuriusjs/federation": "^1.0.1", |
see here: https://github.com/mercurius-js/mercurius-federation/releases
"@nestjs/platform-fastify": "8.4.7", | ||
"@nestjs/testing": "8.4.7", | ||
"@mercuriusjs/federation": "^1.0.0", | ||
"@mercuriusjs/gateway": "^1.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"@mercuriusjs/gateway": "^1.0.0", | |
"@mercuriusjs/gateway": "^1.2.0", |
see here: https://github.com/mercurius-js/mercurius-gateway/releases
"fastify": "4.12.0", | ||
"mercurius": "8.13.2", | ||
"mercurius": "12.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"mercurius": "12.0.0", | |
"mercurius": "12.2.0", |
see here: https://github.com/mercurius-js/mercurius/releases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think there are big changes in these small updates, they should solve small problems 😄, however I wanted to point this out before the release of the new version of the @nestjs/graphql
package🙌
Really cool @kamilmysliwiec - happy to see this, just as I was playing around tonight with upgrading our rather huge application from express to fastify. What's the proper way to install the 'next' versions exactly? I'd love to test it out, and perhaps provide some feedback, if I should stumble upon anything. I've tried following your additions here: https://github.com/nestjs/docs.nestjs.com/pull/2640/files I am getting package dependency conflicts. An example repo showing nest 9 running with graphql and fastify would be nice. More specifically I am getting this error, when trying to pull in the next releases:
|
@simplenotezy you can use the |
Thanks @kamilmysliwiec - I'll do that! |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information