but it looks like password goes through encrypting / salting, so if i change that in the user schema, would that still work?

hiho Matt! 👋 we're currently working on a resetPassword mutation for the email/password authentication provider. with Auth0 you can issue a reset from within the Auth0 settings

Hey graphcool team, what's the state-of-the-art approach when I want to perform operations (concat) or aggregations (max, avg, min, ...) on one or multiple fields in a query?

Currently that would be handled client-side but we're planning to add custom queries for situations like that: https://github.com/graphcool/feature-requests/issues/40

That's a lot of discussion. Thanks!

Hello everyone! To say i'm excited about this project would be an understatement. My friend sent me the link the other day and I was like..."I've been waiting for something like this!". Anyway, I've had an idea similar, but involved custom queries and synching with existing databases, which it looks like is being discussed here.

Two questions: (1) What is the roadmap for custom queries or database integration (2) What are the security guarantees? I know with AWS you can achieve things like HIPAA compliance...can this also or can we back our schema against AWS?

I am starting a company now and currently rewriting the back-end, and am strongly considering using graphcool entirely. Answering those two questions will help me decide the switch. Thanks!

Hey @theraccoun, thanks for your feedback 🙌 great to see that you're as excited as we are! Custom queries is on our roadmap in the coming months. Let me get back to you in PM about the other points you raise.

Thank you Nilan. This is seriously amazing work, congrats to you guys for pulling it off. I will probably continue playing with it today. The security probably won't be a deal breaker but would be good to know. Anyway, look forward to hearing from you when you find out

Sounds awesome Steven! Happy to chat more about your specific security requirements in PM 🙂

Can anyone provide an example of what the a list of Json values looks like as input into a mutation?

the listJson version of this

listString: ["a string", "another string"]

I think it will be the easiest with a GraphQL variable

otherwise you have to escape the JSON manually...

ah that must be what im missing

im trying in the playground but keep getting this error

Variable '$questions' of type 'Json' used in position expecting type '[Json!]'

so [Json!] is a list of JSON values

it's not a JSON list... if that makes sense?

do you really want a list of JSON values?

I thought so... still sort of playing around at this point

right

then you have to provide a list of JSON values to $questions

when i was using reindex I was able to create a field of types other than scalar or nodes.

I thought the Json value was similar here

So you're saying you could have additional requirements to the JSON values?

for example, it should always have a

data

and a

text

property?

essentially yeah, though I'm not sure how it was implemented

you could have a field images of list type of

Image

and

Image

would have a

size, url, filename, etc...

Semantically, you can certainly do that right now with models and relations. Where do you see the benefit in using JSON instead?