Lucas Bento

@phra: our current structure runs this way because we have a CLI tool that abstracts the use of Yeoman. We are going to improve that on our next major version...

A PR will be highly appreciated :)

Not yet, but I'm open to hear ways to do so.

`--config` in Jest works just like our `.graphqlrc`, we need a way to specify multiple GraphQL server paths on our config file.

@femesq: awesome idea, was just thinking about using it also for front-end development, creating mutations from scratch is still a pain in the ass.

How do you guys suggest that we identify if the CLI is running on a front-end or back-end project? We may use the `.graphqlrc` config file but I feel that...

@sibelius: yeah. We should start working on #59 asap.

Interesting, thanks for suggesting it. By experience you mean the prompts? How do you imagine including those here?

Looks good, haven't thought about it because I never had a use case for doing so. Would you mind sharing your use case to come up with that idea?

Humm, I think I got it now. Are you looking for a command to generate an _empty_ model as we currently do on type without schema ([here](https://github.com/lucasbento/create-graphql/blob/master/packages/generator/src/type/templates/Type.js.template))?