Can a GraphQL input type inherit from another type or interface?I dont want to redefine properties when defining a GraphQL type. Is there a way to get past it?GraphQL Schema to handle mixed typesIs it possible to implement multiple interfaces in GraphQL?GraphQL Union and Input Type?GraphQL how to avoid duplicate code between input and output typesDefining ResolveType for GraphQL interfaces from type definition textGraphQL query fragments on interface type implementationsUse same fields for type and input in GraphQLGraphQL nested input extensionsReact, Graphql Select FormOverriding “root” object value of GraphQL Union/Interface type
How can I determine if the org that I'm currently connected to is a scratch org?
Little known, relatively unlikely, but scientifically plausible, apocalyptic (or near apocalyptic) events
How did the Super Star Destroyer Executor get destroyed exactly?
Is it logically or scientifically possible to artificially send energy to the body?
Why do I get two different answers for this counting problem?
Is it acceptable for a professor to tell male students to not think that they are smarter than female students?
Why doesn't using multiple commands with a || or && conditional work?
What method can I use to design a dungeon difficult enough that the PCs can't make it through without killing them?
Ambiguity in the definition of entropy
How badly should I try to prevent a user from XSSing themselves?
What reasons are there for a Capitalist to oppose a 100% inheritance tax?
If human space travel is limited by the G force vulnerability, is there a way to counter G forces?
Why would the Red Woman birth a shadow if she worshipped the Lord of the Light?
I would say: "You are another teacher", but she is a woman and I am a man
How to prevent "they're falling in love" trope
How can saying a song's name be a copyright violation?
Expand and Contract
Can a virus destroy the BIOS of a modern computer?
How to tell a function to use the default argument values?
Why is the ratio of two extensive quantities always intensive?
What's the in-universe reasoning behind sorcerers needing material components?
Zip/Tar file compressed to larger size?
What is the most common color to indicate the input-field is disabled?
Could the museum Saturn V's be refitted for one more flight?
Can a GraphQL input type inherit from another type or interface?
I dont want to redefine properties when defining a GraphQL type. Is there a way to get past it?GraphQL Schema to handle mixed typesIs it possible to implement multiple interfaces in GraphQL?GraphQL Union and Input Type?GraphQL how to avoid duplicate code between input and output typesDefining ResolveType for GraphQL interfaces from type definition textGraphQL query fragments on interface type implementationsUse same fields for type and input in GraphQLGraphQL nested input extensionsReact, Graphql Select FormOverriding “root” object value of GraphQL Union/Interface type
Is it possible to use inheritance with GraphQL input types?
Something like that (this, of course, doesn't work with input types):
interface UserInputInterface
firstName: String
lastName: String
input UserInput implements UserInputInterface
password: String!
input UserChangesInput implements UserInputInterface
id: ID!
password: String
graphql
add a comment |
Is it possible to use inheritance with GraphQL input types?
Something like that (this, of course, doesn't work with input types):
interface UserInputInterface
firstName: String
lastName: String
input UserInput implements UserInputInterface
password: String!
input UserChangesInput implements UserInputInterface
id: ID!
password: String
graphql
1
Have you ever figured out answer to your question? I'm facing the exact same one!
– LB2
May 2 '17 at 19:46
3
@LB2 unfortunately not, I'm keeping 2 separate types at the moment repeating properties.
– kyrisu
May 3 '17 at 9:29
Thanks! I'm trying to represent a boolean expression (much like SQL's WHERE clause), and without inheritance, it seems impossible to express an arbitrary boolean expression without possibility of syntax-matching nonsense. Bummer that it's not part of the language.
– LB2
May 3 '17 at 21:19
add a comment |
Is it possible to use inheritance with GraphQL input types?
Something like that (this, of course, doesn't work with input types):
interface UserInputInterface
firstName: String
lastName: String
input UserInput implements UserInputInterface
password: String!
input UserChangesInput implements UserInputInterface
id: ID!
password: String
graphql
Is it possible to use inheritance with GraphQL input types?
Something like that (this, of course, doesn't work with input types):
interface UserInputInterface
firstName: String
lastName: String
input UserInput implements UserInputInterface
password: String!
input UserChangesInput implements UserInputInterface
id: ID!
password: String
graphql
graphql
asked Jan 29 '17 at 12:57
kyrisukyrisu
2,37573461
2,37573461
1
Have you ever figured out answer to your question? I'm facing the exact same one!
– LB2
May 2 '17 at 19:46
3
@LB2 unfortunately not, I'm keeping 2 separate types at the moment repeating properties.
– kyrisu
May 3 '17 at 9:29
Thanks! I'm trying to represent a boolean expression (much like SQL's WHERE clause), and without inheritance, it seems impossible to express an arbitrary boolean expression without possibility of syntax-matching nonsense. Bummer that it's not part of the language.
– LB2
May 3 '17 at 21:19
add a comment |
1
Have you ever figured out answer to your question? I'm facing the exact same one!
– LB2
May 2 '17 at 19:46
3
@LB2 unfortunately not, I'm keeping 2 separate types at the moment repeating properties.
– kyrisu
May 3 '17 at 9:29
Thanks! I'm trying to represent a boolean expression (much like SQL's WHERE clause), and without inheritance, it seems impossible to express an arbitrary boolean expression without possibility of syntax-matching nonsense. Bummer that it's not part of the language.
– LB2
May 3 '17 at 21:19
1
1
Have you ever figured out answer to your question? I'm facing the exact same one!
– LB2
May 2 '17 at 19:46
Have you ever figured out answer to your question? I'm facing the exact same one!
– LB2
May 2 '17 at 19:46
3
3
@LB2 unfortunately not, I'm keeping 2 separate types at the moment repeating properties.
– kyrisu
May 3 '17 at 9:29
@LB2 unfortunately not, I'm keeping 2 separate types at the moment repeating properties.
– kyrisu
May 3 '17 at 9:29
Thanks! I'm trying to represent a boolean expression (much like SQL's WHERE clause), and without inheritance, it seems impossible to express an arbitrary boolean expression without possibility of syntax-matching nonsense. Bummer that it's not part of the language.
– LB2
May 3 '17 at 21:19
Thanks! I'm trying to represent a boolean expression (much like SQL's WHERE clause), and without inheritance, it seems impossible to express an arbitrary boolean expression without possibility of syntax-matching nonsense. Bummer that it's not part of the language.
– LB2
May 3 '17 at 21:19
add a comment |
1 Answer
1
active
oldest
votes
No, the spec does not allow input types to implement interfaces. And GraphQL type system in general does not define any form of inheritance. Even interfaces can not inherit other interfaces. The spec is intentionally constrained to stay simple. This means that you're stuck repeating fields across input types.
That said, depending on the way you construct your schema, you could build some kind of type transformer that appends the common fields programmatically based on some meta-data, e.g. a directive.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f41921137%2fcan-a-graphql-input-type-inherit-from-another-type-or-interface%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
No, the spec does not allow input types to implement interfaces. And GraphQL type system in general does not define any form of inheritance. Even interfaces can not inherit other interfaces. The spec is intentionally constrained to stay simple. This means that you're stuck repeating fields across input types.
That said, depending on the way you construct your schema, you could build some kind of type transformer that appends the common fields programmatically based on some meta-data, e.g. a directive.
add a comment |
No, the spec does not allow input types to implement interfaces. And GraphQL type system in general does not define any form of inheritance. Even interfaces can not inherit other interfaces. The spec is intentionally constrained to stay simple. This means that you're stuck repeating fields across input types.
That said, depending on the way you construct your schema, you could build some kind of type transformer that appends the common fields programmatically based on some meta-data, e.g. a directive.
add a comment |
No, the spec does not allow input types to implement interfaces. And GraphQL type system in general does not define any form of inheritance. Even interfaces can not inherit other interfaces. The spec is intentionally constrained to stay simple. This means that you're stuck repeating fields across input types.
That said, depending on the way you construct your schema, you could build some kind of type transformer that appends the common fields programmatically based on some meta-data, e.g. a directive.
No, the spec does not allow input types to implement interfaces. And GraphQL type system in general does not define any form of inheritance. Even interfaces can not inherit other interfaces. The spec is intentionally constrained to stay simple. This means that you're stuck repeating fields across input types.
That said, depending on the way you construct your schema, you could build some kind of type transformer that appends the common fields programmatically based on some meta-data, e.g. a directive.
edited Mar 29 at 13:45
answered Aug 7 '17 at 19:27
kaqqaokaqqao
6,19623981
6,19623981
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f41921137%2fcan-a-graphql-input-type-inherit-from-another-type-or-interface%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Have you ever figured out answer to your question? I'm facing the exact same one!
– LB2
May 2 '17 at 19:46
3
@LB2 unfortunately not, I'm keeping 2 separate types at the moment repeating properties.
– kyrisu
May 3 '17 at 9:29
Thanks! I'm trying to represent a boolean expression (much like SQL's WHERE clause), and without inheritance, it seems impossible to express an arbitrary boolean expression without possibility of syntax-matching nonsense. Bummer that it's not part of the language.
– LB2
May 3 '17 at 21:19