Dude, not only you do full scale videos on developing real world apps with GraphQL, but you also care about us, noobs who are learning tech from the very beginning. Bravo! Good job!
"No Demon"!! lol. I had to stop and think. I've always prounouced it node-mon (short for node monitor) This is not a critique, just always funny to hear how others in the community sound things out differently than you do, and it's always and instant... "wait what?" and then down the rabbit hole you go.... I love your stuff! I'm a software development coach, and I often refer my students/teams to your stuff when they need to quickly form a basic foundation around a concept.
@Ben , Whether Persisted graphql query can improve performance? what is your thought on this? which are the other ways to improve graphql API performance? please suggest
Do you know if there is a way to group mutations and queries in the schema tab? It would be nice if i could see all the mutations that belong to authentication for example. The way I'm doing it now is just by naming my mutations with auth_login, auth_logout for example. It just would be a lot nicer if i didn't have to name them this way.
How do you handle dictionaries / map types with graphql? They are a fundamental data structure and I dont like that idea of using a scalar type/string to move dictionaries from server->client
Dude, not only you do full scale videos on developing real world apps with GraphQL, but you also care about us, noobs who are learning tech from the very beginning. Bravo! Good job!
"No Demon"!! lol. I had to stop and think. I've always prounouced it node-mon (short for node monitor)
This is not a critique, just always funny to hear how others in the community sound things out differently than you do, and it's always and instant... "wait what?" and then down the rabbit hole you go....
I love your stuff! I'm a software development coach, and I often refer my students/teams to your stuff when they need to quickly form a basic foundation around a concept.
best coding youtuber e v e r, thanks mate
Everything made sense to me. Thank you for using a simple but _practical_ example 👍
Love how active you are with uploading.
Now is it:
no - demon
or
node - mon
thanks and I have no idea
Great! I hope you will cover basic apollo on frontend as well! :D
It's not going to be included in this series, but I have other videos on it and plan on doing more in the future
Thanks Ben Im tracking you and loving Graphql
tyvm mate! looking forward for the next videos
a goodie i cant wait to div into this one
@Ben , Whether Persisted graphql query can improve performance? what is your thought on this? which are the other ways to improve graphql API performance? please suggest
Nice tutorial thanks !
Great Video, Thank you for sharing
Send you lots of love and thanks.
Great video, I love your content!
nice. are you going to slowly transition the series to typescript?
this one is focused on graphql, so it's going to stay javascript to keep it simple
swt man, im a long time .net dev, but newbie to node and ur world, so loving ur content. keep up the great work!
no demon!)) Nice)
this is great
Do you know if there is a way to group mutations and queries in the schema tab? It would be nice if i could see all the mutations that belong to authentication for example. The way I'm doing it now is just by naming my mutations with auth_login, auth_logout for example. It just would be a lot nicer if i didn't have to name them this way.
You could try doing something like this: gist.github.com/benawad/6ca6332ff64590e3e8f4346a03ab20f0
How do you handle dictionaries / map types with graphql? They are a fundamental data structure and I dont like that idea of using a scalar type/string to move dictionaries from server->client
if you don't know the keys, you'll have to create a scalar or string otherwise you can create an Object type
Can you plz again Explain the concept of Mutation, Resolvers, and Queries??? Plzzzzzzzzzzz
Query is a type where you put fields that don't write data. If it does write data you put it in Mutation
resolvers are tomorrows topic
@@bawad Thanks
Would you agree that express-graphql is now obsolete?
github.com/graphql/express-graphql
I don't see much activity on this project.
hard to say, I haven't been following the project closely, so I'm not sure why they are pausing development
I found this:
github.com/graphql/express-graphql/issues/480
Interesting, looks like it's dead for at least the next couple months
First time I hear someone pronounce nodemon as 'node-demon'
no demon > node mon
no demon
UserInputError ;)
haha. it's 'node + mon'. not 'no + demon'
Hi Ben,
I'm not able to write graphql schema for below json...
Issue is "212561731" is key and value is object
const response = {
usedInventoryResponsesMap: {
"212561731": {
usedInventoryDetails: [
{
consignmentNumber: "106104370",
consignmentType: "G",
debriefDate: null,
declarationStatus: "N",
errorCode: null,
errorDescription: null,
icvPrice: "278",
itemId: "3249431",
listPrice: "278",
locatorId: "5841415",
orderDate: "2023-03-14 21:33:55.0",
organization_code: "SUS",
partAged: "71",
partDescription:
"FRU - VFD EPM chip for a Price Pump in the 5161931 Heat Exchanger Cabinet",
partNumber: "5443037",
partType: "GP CONSUMABLES",
qtyAvailableToDebrief: "1",
returnQuantity: "1",
returnReferenceNumber: "356143051",
returnType: "Def/FOI-Recycle;Good-Green;WP/FOA-Red",
returnTypeFlag: "G",
rfsNumber: "1-547295414631",
serialNumber: null,
shipDate: "2023-03-15 02:49:25.0",
systemId: "407OSCMR2",
transactionQuantity: "1",
warehouse: null,
avl_to_declare_qtye: "1",
},
],
},
},
};