What do you think if we can make the Permission part into code instead of click and click in the dashboard?

the forum is actually down but I think it was two days ago the new CLI in beta as been announced and you can manage your permissions and everything from you project with it. Actually you don’t use the console.graph.cool anymore (just to visualise your data if you want) you can download use the new CLI with

npm install -g graphcool@beta

and then you have the

graphcool init

command to dump all your projects in files in your codebase 😉

@LeiZeng I'll share the forum post as soon as possible - you should read it before installing and using the CLI 🙂

@antho1404 Wow, thanks for sharing, Ill have a try.

It’s still in beta now, I’m sure there is more doc coming

@LeiZeng check https://www.graph.cool/forum/t/feedback-new-cli-beta/949?u=nilan for more information 🙂

Thanks @antho1404, I just have a feedback about the query files. I would suggest to use some name convention instead of hash, like Type-operation(User-read.graphql), the hash file name really bothering me in the text editor...

@nilan great the forum is online again @LeiZeng I was thinking the same but the file will be terrible because you cannot constrain with just type + operation, sometime you want to have specific permissions for fields and you can have multiple

user-read

in this case so I think just name your file is the most flexible way.

I can manage them at my end, once its code, I have the control anyway, but just please think about it.

@LeiZeng could you add this comment to the Forum? 🙂

sure

yes i will answer it 😉 I have a good architecture wich is quite clear and you may like it

that will be great.