-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
Add federation #314
Add federation #314
Conversation
8166383
to
9cace27
Compare
f4eaa94
to
a01dc0a
Compare
a01dc0a
to
9aefc0e
Compare
@ghostdogpr comments addressed! |
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.
Just some tiny nitpicking comments.
I don't understand 100% of federation but this looks pretty good, in particular the fact you could do it on top of the current implementation without modifying the core much.
vuepress/docs/docs/federation.md
Outdated
To use, add the following line to your `build.sbt` file: | ||
|
||
``` | ||
libraryDependencies += "com.github.ghostdogpr" %% "caliban-federation" % "0.7.3" |
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.
Can you make it 0.7.4
? So that next time I release, a find & replace will find it 😄
federation/src/main/scala/caliban/federation/EntityResolver.scala
Outdated
Show resolved
Hide resolved
bbabbe9
to
b6ae340
Compare
All good, thanks for adding this! |
This PR adds federation to caliban. ATM it is still a WIP but I wanted to open the PR early to get feedback on the approach.
More info on the federation spec can be found here.
There are a couple pieces that are still missing in no particular order:
Federated schema validation(Handled by the gateway)Error handling(Same as normal graphql)EntityResolvers
more ergonomic (automatic generation?)