hi hi - so with the new CLI tooling, it means we a...
# prisma-whats-new
w
hi hi - so with the new CLI tooling, it means we abandon all the UI on graph.cool if we choose to use it?
a
If you want to, you can work completely without the UI. The only feature 'unique' to the Console is the Databrowser at the moment.
w
can I do my functions locally, but still use the UI console for everything else?
I really like the console, I just want to have 100% of everything in git
I rather not hand code all my permissions and realtionships
a
That's not possible unfortunately
w
😞 arg
a
However, you can use the new Playground in the Console to create your permission queries
w
ohh really
a
Yep, there's a little key symbol at the top to access the permission editor
It's only available in the console version (for now)
w
http://wes.io/nMeG I see this - but what do I do?
ohh the editor broke 🙂
a
Yeah, known issue, refresh the page
w
man thats a bummer that you have to go all in -I just want the ability to have my functions local and keep everything else the same
the UI is so nice for managing permissions
a
Once you get used to the CLI way of managing permissions, it's actually quite easy, especially with the new permission editor in the playground.
w
Yeah? I’ll give it a shot and see how it goes -thanks for your help
k
@nilan ☝️ that conversation is literally me when you told me about your future plans 😄 The console was 💯. It was so easy to manage all the data, permissions, relationships… Good times 😿
w
Yeah it’s too bad you can’t sync everything
wait you can’t even add data via the console?
a
I think either Graphcool or the community will move that functionality into IDE plugins (Atom, Cloud9). I have been working on some Cloud9 plugins to give you some panels that are similar to the console.
Yes, the databrowser will still be available!
Playground, Schema Viewer, Data Browser, Function logs, Permission Viewer
w
the deploy is really slow too 😕
takes ~4 mins everytime I change something
going to be a really slow feedback loop for function dev
a
Wow, it only takes seconds for me. Do you have a really large project folder? Maybe your front-end in there as well?
w
Yeah - should this be in a separate directory?
oh that that sped it up - thanks!
a
Yes, the bundler packages the entire folder, so make sure to keep only your Graphcool project in there!
w
So would I have two package.json files then? One for my app front end and one for graphcool?
a
Yes, just keep the graphcool project in a subfolder with it's own package.json
w
okay cool
a
Because it will package the entire node_modules folder, which can be quite big with frontend deps in there
m
@wesbos Give the new framework a try - it’s been a ride, but this shift is really good overall.
👍🏻 1
w
@mwickett thanks - I’m coming around to it 🙂
n
we definitely need to improve the documentation around having a separate folder for your service definition - see https://github.com/graphcool/framework/issues/837 for a long term solution, too