As a software developer this guy is a great salesman (for the tools he wants people to use). Maybe he isn't doing in purpose, but he would do great in sales 😄 "Be a champ for my project" "Do not use basic software, use our services"
This was entirely a marketing presentation. I was hoping to learn something about the ins and outs of schema design but it really comes down to "hey look at what our tooling and platform can give you".
I'm trying to figure out how to sort by asc in my resolver, on a subdocument Kitchen Schema, { itemCategory } and { itemName }, can sort by directly querying the Kitchen Schema, but when quiring the context user, (me) and the subdocument field kitchen ref: 'Kitchen'. the itemCategory and itemName are not sorting at all.
So it seems GraphQL should cater to the client(s). One specific thing I have in mind, in storing monetary data. We believe it would be best to store it in "cents" as an integer ie 3500 = $35, 3555 = $35.55. With that in mind, should GraphQL input/output monetary values as Int or a Float as that is what the client would be using?
I don't work at Apollo, but I think you should use integers. While the graph can make things easier for clients, it shouldn't make things ambiguous or wrong.
We input as integer, and output as a type called Money. This Money type contains several fields: currency, formatted amount (which is a string like "€5.00") and lastly: amount (which is the original input as an integer).
As a software developer this guy is a great salesman (for the tools he wants people to use). Maybe he isn't doing in purpose, but he would do great in sales 😄
"Be a champ for my project"
"Do not use basic software, use our services"
Watson's the best
This was entirely a marketing presentation. I was hoping to learn something about the ins and outs of schema design but it really comes down to "hey look at what our tooling and platform can give you".
And the rabbit hole never ends!!!! Thanks Michael for turning on the lights for a lot more rooms to explore!!!!
Could we please get a code example for filtering criteria as variables for the graph?
You go Michael Watson!
I'm trying to figure out how to sort by asc in my resolver, on a subdocument
Kitchen Schema, { itemCategory } and { itemName }, can sort by directly querying the Kitchen Schema, but when quiring the context user, (me) and the subdocument field kitchen ref: 'Kitchen'. the itemCategory and itemName are not sorting at all.
So it seems GraphQL should cater to the client(s).
One specific thing I have in mind, in storing monetary data. We believe it would be best to store it in "cents" as an integer ie 3500 = $35, 3555 = $35.55.
With that in mind, should GraphQL input/output monetary values as Int or a Float as that is what the client would be using?
I don't work at Apollo, but I think you should use integers. While the graph can make things easier for clients, it shouldn't make things ambiguous or wrong.
Hey, use integers. Is the way stripe does it and is really great
We input as integer, and output as a type called Money. This Money type contains several fields: currency, formatted amount (which is a string like "€5.00") and lastly: amount (which is the original input as an integer).
basically its the same as monogdb lol.. cater the api/db to the calls
The one single downvote is from a REST sympathiser.
Jokes aside, good talk.