Unknown argument: boilerplate about react-fullstack-graphql

[hankolsen]

@jonathanMor Just run graphql create my-app, you will get a list of available boilerplates to choose from automatically :)

[rolandpeelen]

the react-fullstack-advanced isn't available though

[eaco-andrew]

The list isn't showing react-fullstack-advanced as an option

[erikAlon]

Same issue but running graphql create my-app offers the list of boilerplates, specifically react-fullstack-basic as of today.

[hyochan]

@erikAlon is right. There is no --boilerplate today. The doc should be updated.

[sonugk]

Did you guys manage to find a solution?
#550 (comment)

As mentioned by @jonathanMor "Just run graphql create my-app"
Also upvote his comment so that everyone can see

[hankolsen]

I have the same problem :(

[hankolsen]

@eaco-andrew, I noticed that too and there is another issue regarding that

[hankolsen]

Urigo/graphql-cli#384

[kiano0sh]

I'm facing this problem too and also there's no react-fullstack-advanced option.

[thidasapankaja]

Is there a way to get this fixed ?

[sonugk]

@jonathanMor Just run graphql create my-app, you will get a list of available boilerplates to choose from automatically :)

This one worked for me

[Timonzimm]

Did you guys manage to find a solution?

[sonugk]

the react-fullstack-advanced isn't available though

#550 (comment)

As mentioned by @jonathanMor "Just run graphql create my-app"
Also upvote his comment so that everyone can see

[Timonzimm]

As mentioned by @rolandpeelen, "the react-fullstack-advanced isn't available though".

[pvijeh]

i opened a PR to remove this flag from the documentation
#686

[chris-hailstorm]

I can't vouch for the current state of the react-fullstack-advanced boilerplate, but it's easy enough to enable that variant for the CLI tool. After an npm install of graphql-cli, just edit the boilerplate list in node_modules/graphql-cli/dist/cmds/create/boilerplates.js and add an entry in the same form as the ones for /minimal and /basic, then run graphql create.

Maybe the exclusion of the react-fullstack-advanced boilerplate was intentional because the boilerplate itself isn't ready; I can't tell. But the names and URLs are all hardwired in that file.