Federation

[sgentile]

I like what I'm seeing - I'm curious - I need to be able to add attributes for federation support

ie sample schema:

type Post @key(fields: "id") {
  id: ID!
  title: String!
  content: String!
  published: Boolean!
  createdAt: String!
  userId: Int
  user: User
}


extend type Query {
  posts: [Post!]!
  post(id: ID!): Post
}

extend type User @key(fields: "id") {
  id: ID! @external
  posts: [Post]
}

Is this possible ?

[sgentile]

I'd need to add 'key', 'extend' and 'external' support

[unlight]

Generator rely on code first approach https://docs.nestjs.com/graphql/federation#code-first
There is generator option https://github.com/unlight/prisma-nestjs-graphql#decorate which can add any decorator to any type
I'll try to provide example.

[unlight]

O, currently is not possible decorate is adding decorators for field in class, not for class itself.

[unlight]

@sgentile
Could you describe your case?
I added manually keys, extend, external directives, but nothing is changed in schema.
Are you using several prisma schemas, own schema for each service?

[sgentile]

Recommend reading here https://docs.nestjs.com/graphql/federation

Note the resolve reference as well

yes to your question - federation has a gateway and multiple services that are used with one Apollo endpoint that basically provides a router and knows how to fetch relationships.

I have an example https://github.com/sgentile/nest-apollo-federation

But in my example all the resolvers and prisma is manual - I want this to have the generator but need to extend the models/scheme with the additional items used by federation

[unlight]

@sgentile
Example should work with next version

/// @NG.Directive('@extends')
/// @NG.Directive('@key(fields: "id")')
model User {
    /// @NG.Directive('@external')
    id String @id
}

generator nestgraphql {
    fields_NG_from = "@nestjs/graphql"
    fields_NG_output = false
    fields_NG_model = true
}

[unlight]

🎉 This issue has been resolved in version 14.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sgentile]

Thank you!

Question.... and I probably overlooked this: Apply 'extends' and @key is great' there is another use case with this - you can see this in the post schema:

extend type User @key(fields: "id") {
  id: ID! @external
  posts: [Post]
}

This User type is not part of 'Posts' Prisma schema, however this is what links the above user model as shown here:
https://github.com/sgentile/nest-apollo-federation/blob/main/posts-service/src/posts/schema.graphql

Just for reference this is then used in the resolver- ie.:
@ResolveField('user')
getUser(@parent() post: Post) {
return { __typename: 'User', id: post.userId };
}