looking for some solutions? You are welcome.

SOLVED: I dont want to redefine properties when defining a GraphQL type. Is there a way to get past it? [duplicate]

yasin:

This question already has an answer here:

principal

interface Community {
  uuid: String
  name: String
  tagline: String
  desc: String
  location: String
}

his children

type CommunityWithOwnerUser implements Community {
  uuid: String
  name: String
  tagline: String
  desc: String
  location: String
  //....owner details
  ownerUuid:String
  ownerName:String
}

other child

type CommunityWithAnyMember implements Community {
  uuid: String
  name: String
  tagline: String
  desc: String
  location: String
  //....member details
  memberUuid:String
  memberName:String
}

I know that these types are unreasonable.it is example

my question

I've rewritten the details of the Community type in all type definitions. instead it would be great if I could use something like extend

type CommunityWithAnyMember extend Community {
  memberUuid:String
  memberName:String
}

its output

type CommunityWithAnyMember {
  uuid: String
  name: String
  tagline: String
  desc: String
  location: String
  memberUuid:String
  memberName:String
}

I've been doing research for a long time. I found https://github.com/Sydsvenskan/node-graphql-partials but it didn't help.Thank you for your answer



Posted in S.E.F
via StackOverflow & StackExchange Atomic Web Robots
Share:

No comments:

Recent