-
Notifications
You must be signed in to change notification settings - Fork 383
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: add apollo federation support #301
Conversation
When will this pull request be accepted? |
@kamilmysliwiec what's your opinion about this? |
When is this going to be added. Super important feature. |
Seems absurd that PRs are open for weeks without any response from core contributors. |
Thanks @marcus-sa for this very valuable input 😄 This feature looks very promising. I'll look at it shortly |
Great idea! Could you add an integration test for this? Also, would you like to create a PR to the documentation with a sample usage? :) Adding an example to nestjs/nest repo ( |
Sure, I'll do that tomorrow 😁 |
Any updates? should i keep pushing again super necessary for greenfield projects. |
@brianschardt there's been some API changes to Apollo Federation that I have to look at first, and then update the PR accordingly :) https://blog.apollographql.com/announcing-managed-federation-265c9f0bc88e |
Any news about this ? |
@sukei been busy at work and with other projects, but essentially I'm waiting for TypeGraphQL to support custom directives which is required by Apollo Federation. |
@marcus-sa it would really be great to be able to merge this without waiting for the code-first support |
} = this.options; | ||
const app = httpAdapter.getInstance(); | ||
|
||
const typeDefs = await this.graphqlTypesLoader.getTypesFromPaths(typePaths); |
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.
@marcus-sa just a little question, why are u here getting types instead of merging them with mergeTypesByPaths like in graphql.module.ts ?
Hey Guys, just wondering how this is looking? Is there anything still blocking this. I agree with @eole1712 above, when TypeGraphQL comes out with support, can look at another pull request to implement that. |
I want to switch from PHP (laravel) to NestJS but this is a show stopper. What's the current state? |
I just forked it and merged this pull request into my fork and using the fork in the interim, as hopefully before we go live, it will be merged with master. |
I forked the fork from @marcus-sa and tried to get it running with
How to reproduce: First I adjusted the package.json file to contain this line:
Then executed those commands: mkdir -p lib/graphql
git clone https://github.com/marcus-sa/graphql.git lib/graphql
cd lib/graphql
npm i && npm audit fix
npm run build
cd ../..
rm -rf node_modules package-lock.json
npm i
npm run start:debug I also tried to add the lib folder within my project tsconfig.json to exclude but makes no difference. |
Thanks to @tuxmachine for following up on it. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Note: doesn't support
type-graphql
because of Apollo's custom directivesPR 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?
#299
#288
What is the new behavior?
Support for Apollo Federation
Does this PR introduce a breaking change?
Other information