Problem
Currently one needs to always go to the documentation website to read the configuration parameters and then set them up in the configuration file. We want to leverage IDE capabilities for GraphQL to provide intellisense and improve developer experience.
Solution
Create a new tc init command that bootstraps a tailcall project:
-
Creates a .tailcallrc.graphql like this
-
Asks the user if they want to add a file to the project if they say no - exit with just the .tailcallrc.graphql file, otherwise if they say yes:
-
Asks the user to enter a the file name and create a <file name>.graphql file.
-
Create a .graphqlrc.yml file with the following content
schema:
- "./<file name>.graphql"
- "./.tailcallrc.graphql"
Problem
Currently one needs to always go to the documentation website to read the configuration parameters and then set them up in the configuration file. We want to leverage IDE capabilities for GraphQL to provide intellisense and improve developer experience.
Solution
Create a new
tc initcommand that bootstraps a tailcall project:Creates a
.tailcallrc.graphqllike thisAsks the user if they want to add a file to the project if they say no - exit with just the
.tailcallrc.graphqlfile, otherwise if they say yes:Asks the user to enter a the file name and create a
<file name>.graphqlfile.Create a
.graphqlrc.ymlfile with the following content