Prisma graphql computed fields2019 Community Moderator ElectionSchema Stitching two remote Prisma/GraphQL schemasHow to send a GraphQL Query from Node.js to PrismaPrisma: What's the workflow?Access Control Filtering of Query before its sent to Prisma server/DBCorrect way to declare fields for Prisma provided by GraphQL Yoga but not required in resolver“Virtual” or manipulated response values in GraphQL using prisma and yogaUnable to use Fragments on GraphQL-yoga with PrimsaRow level security using prisma and postgresPrisma append custom field to info argument when querying dataHow to create nested connection in prisma query?
The (Easy) Road to Code
Yet another question on sums of the reciprocals of the primes
School performs periodic password audits. Is my password compromised?
What is the purpose of a disclaimer like "this is not legal advice"?
Has a sovereign Communist government ever run, and conceded loss, on a fair election?
What is this tube in a jet engine's air intake?
How can a demon take control of a human body during REM sleep?
Is it possible to clone a polymorphic object without manually adding overridden clone method into each derived class in C++?
What was so special about The Piano that Ada was willing to do anything to have it?
How do spaceships determine each other's mass in space?
Create chunks from an array
Finding the minimum value of a function without using Calculus
ESPP--any reason not to go all in?
Under what conditions can the right to be silence be revoked in the USA?
If nine coins are tossed, what is the probability that the number of heads is even?
Cycles on the torus
Professor forcing me to attend a conference, I can't afford even with 50% funding
Rationale to prefer local variables over instance variables?
Use Mercury as quenching liquid for swords?
Sampling from Gaussian mixture models, when are the sampled data independent?
Is it a Cyclops number? "Nobody" knows!
What does *dead* mean in *What do you mean, dead?*?
Would those living in a "perfect society" not understand satire
Is there a way to make cleveref distinguish two environments with the same counter?
Prisma graphql computed fields
2019 Community Moderator ElectionSchema Stitching two remote Prisma/GraphQL schemasHow to send a GraphQL Query from Node.js to PrismaPrisma: What's the workflow?Access Control Filtering of Query before its sent to Prisma server/DBCorrect way to declare fields for Prisma provided by GraphQL Yoga but not required in resolver“Virtual” or manipulated response values in GraphQL using prisma and yogaUnable to use Fragments on GraphQL-yoga with PrimsaRow level security using prisma and postgresPrisma append custom field to info argument when querying dataHow to create nested connection in prisma query?
I have this datamodel:
type Item
id: ID! @unique
title: String!
description: String!
user: User!
pictures: [Picture]
basePrice: Int!
addons: [Addon]
I'm writing a query called parsedItem that takes the id from arguments and looks for the Item (using the default query for Item generated by Prisma), something like this:
const where = id: args.id ;
const item = await ctx.db.query.item( where ,
`{
id
title
...
I need to show on the frontend a computed value: "dynamicPrice" it depends on the quantity of the Addons that the Item has.
e.g:
Item #1 has 3 addons, each addons has a value of $5. This calculated value should be
dynamicPrice = basePrice + 3 * 5
The Addon relation could change, so I need to compute this in every request the frontend makes.
I'd like so much to do something like:
item.dynamicPrice = item.basePrice + (item.addons.length * 5)
and return this item in the resolver, but this doesn't work. That throw an error:
"message": "Cannot query field "dynamicPrice" on type "Item"."
(when I try to query the Item from the frontend)
This error message makes me think: Should I create dynamicPrice as a field on the datamodel? Can I then populate this field in the query resolver? I know I can, but is this a good approach?
This is an example, I need to create more computed values for this Item model.
What is the best scalable solution/workaround for this simple use case?
graphql apollo apollo-client prisma prisma-graphql
add a comment |
I have this datamodel:
type Item
id: ID! @unique
title: String!
description: String!
user: User!
pictures: [Picture]
basePrice: Int!
addons: [Addon]
I'm writing a query called parsedItem that takes the id from arguments and looks for the Item (using the default query for Item generated by Prisma), something like this:
const where = id: args.id ;
const item = await ctx.db.query.item( where ,
`{
id
title
...
I need to show on the frontend a computed value: "dynamicPrice" it depends on the quantity of the Addons that the Item has.
e.g:
Item #1 has 3 addons, each addons has a value of $5. This calculated value should be
dynamicPrice = basePrice + 3 * 5
The Addon relation could change, so I need to compute this in every request the frontend makes.
I'd like so much to do something like:
item.dynamicPrice = item.basePrice + (item.addons.length * 5)
and return this item in the resolver, but this doesn't work. That throw an error:
"message": "Cannot query field "dynamicPrice" on type "Item"."
(when I try to query the Item from the frontend)
This error message makes me think: Should I create dynamicPrice as a field on the datamodel? Can I then populate this field in the query resolver? I know I can, but is this a good approach?
This is an example, I need to create more computed values for this Item model.
What is the best scalable solution/workaround for this simple use case?
graphql apollo apollo-client prisma prisma-graphql
add a comment |
I have this datamodel:
type Item
id: ID! @unique
title: String!
description: String!
user: User!
pictures: [Picture]
basePrice: Int!
addons: [Addon]
I'm writing a query called parsedItem that takes the id from arguments and looks for the Item (using the default query for Item generated by Prisma), something like this:
const where = id: args.id ;
const item = await ctx.db.query.item( where ,
`{
id
title
...
I need to show on the frontend a computed value: "dynamicPrice" it depends on the quantity of the Addons that the Item has.
e.g:
Item #1 has 3 addons, each addons has a value of $5. This calculated value should be
dynamicPrice = basePrice + 3 * 5
The Addon relation could change, so I need to compute this in every request the frontend makes.
I'd like so much to do something like:
item.dynamicPrice = item.basePrice + (item.addons.length * 5)
and return this item in the resolver, but this doesn't work. That throw an error:
"message": "Cannot query field "dynamicPrice" on type "Item"."
(when I try to query the Item from the frontend)
This error message makes me think: Should I create dynamicPrice as a field on the datamodel? Can I then populate this field in the query resolver? I know I can, but is this a good approach?
This is an example, I need to create more computed values for this Item model.
What is the best scalable solution/workaround for this simple use case?
graphql apollo apollo-client prisma prisma-graphql
I have this datamodel:
type Item
id: ID! @unique
title: String!
description: String!
user: User!
pictures: [Picture]
basePrice: Int!
addons: [Addon]
I'm writing a query called parsedItem that takes the id from arguments and looks for the Item (using the default query for Item generated by Prisma), something like this:
const where = id: args.id ;
const item = await ctx.db.query.item( where ,
`{
id
title
...
I need to show on the frontend a computed value: "dynamicPrice" it depends on the quantity of the Addons that the Item has.
e.g:
Item #1 has 3 addons, each addons has a value of $5. This calculated value should be
dynamicPrice = basePrice + 3 * 5
The Addon relation could change, so I need to compute this in every request the frontend makes.
I'd like so much to do something like:
item.dynamicPrice = item.basePrice + (item.addons.length * 5)
and return this item in the resolver, but this doesn't work. That throw an error:
"message": "Cannot query field "dynamicPrice" on type "Item"."
(when I try to query the Item from the frontend)
This error message makes me think: Should I create dynamicPrice as a field on the datamodel? Can I then populate this field in the query resolver? I know I can, but is this a good approach?
This is an example, I need to create more computed values for this Item model.
What is the best scalable solution/workaround for this simple use case?
graphql apollo apollo-client prisma prisma-graphql
graphql apollo apollo-client prisma prisma-graphql
edited Mar 6 at 21:32
Adrián E.
asked Mar 6 at 21:07
Adrián E.Adrián E.
3091415
3091415
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You need create field resolver for dynamicPrice field at Item type. It will looks like that:
const resolvers =
Query:
parsedItem: (parent, args, ctx, info) =>
...
...
,
Item:
dynamicPrice: parent => parent.basePrice + parent.addons.length * 5
More details you can find at A Guide to Common Resolver Patterns.
It seems that this is the best way, I had to move some parts because of the structure of my project but I ended up using fragment like the documentation says. Thanks @galkin
– Adrián E.
2 days ago
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%2f55032153%2fprisma-graphql-computed-fields%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
You need create field resolver for dynamicPrice field at Item type. It will looks like that:
const resolvers =
Query:
parsedItem: (parent, args, ctx, info) =>
...
...
,
Item:
dynamicPrice: parent => parent.basePrice + parent.addons.length * 5
More details you can find at A Guide to Common Resolver Patterns.
It seems that this is the best way, I had to move some parts because of the structure of my project but I ended up using fragment like the documentation says. Thanks @galkin
– Adrián E.
2 days ago
add a comment |
You need create field resolver for dynamicPrice field at Item type. It will looks like that:
const resolvers =
Query:
parsedItem: (parent, args, ctx, info) =>
...
...
,
Item:
dynamicPrice: parent => parent.basePrice + parent.addons.length * 5
More details you can find at A Guide to Common Resolver Patterns.
It seems that this is the best way, I had to move some parts because of the structure of my project but I ended up using fragment like the documentation says. Thanks @galkin
– Adrián E.
2 days ago
add a comment |
You need create field resolver for dynamicPrice field at Item type. It will looks like that:
const resolvers =
Query:
parsedItem: (parent, args, ctx, info) =>
...
...
,
Item:
dynamicPrice: parent => parent.basePrice + parent.addons.length * 5
More details you can find at A Guide to Common Resolver Patterns.
You need create field resolver for dynamicPrice field at Item type. It will looks like that:
const resolvers =
Query:
parsedItem: (parent, args, ctx, info) =>
...
...
,
Item:
dynamicPrice: parent => parent.basePrice + parent.addons.length * 5
More details you can find at A Guide to Common Resolver Patterns.
answered Mar 6 at 23:22
galkingalkin
2,53121437
2,53121437
It seems that this is the best way, I had to move some parts because of the structure of my project but I ended up using fragment like the documentation says. Thanks @galkin
– Adrián E.
2 days ago
add a comment |
It seems that this is the best way, I had to move some parts because of the structure of my project but I ended up using fragment like the documentation says. Thanks @galkin
– Adrián E.
2 days ago
It seems that this is the best way, I had to move some parts because of the structure of my project but I ended up using fragment like the documentation says. Thanks @galkin
– Adrián E.
2 days ago
It seems that this is the best way, I had to move some parts because of the structure of my project but I ended up using fragment like the documentation says. Thanks @galkin
– Adrián E.
2 days ago
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%2f55032153%2fprisma-graphql-computed-fields%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