feat: tailcall init should be interactive about tailcall

[webbdays]

@varshith257
let tailcallrc = include_str!("../../generated/.tailcallrc.graphql");
let tailcallrc_json: &str = include_str!("../../generated/.tailcallrc.schema.json");

[tusharmath]

/bounty 50$

[algora-pbc]

💎 $50 bounty • Tailcall Inc.

Steps to solve:

1. Start working: Comment /attempt #2195 with your implementation plan
2. Submit work: Create a pull request including /claim #2195 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

🙏 Thank you for contributing to tailcallhq/tailcall!
🧐 Checkout our guidelines before you get started.
💵 More about our bounty program.

Attempt	Started (GMT+0)	Solution
🔴 @varshith257	Jun 14, 2024, 3:35:20 PM	WIP
🟢 @mayankt18	Jun 15, 2024, 8:31:08 AM	WIP
🔴 @be-hunter	Jun 23, 2024, 12:18:44 PM	WIP

[varshith257]

/attempt #2195
@tusharmath Using inquire library for it

Options

• Cancel my attempt

[amitksingh1490]

It should also generate a base configuration file for a "Hello, World!" GraphQL server, similar to how cargo init creates a new project.

[varshith257]

@amitksingh1490 Almost everything is done. While generating user-selected file, do we need to create empty files or existing files - .tailcallrc.graphql - .tailcallrc.schema.json - .graphqlrc.yml in our project?

[webbdays]

comes from source code.

[mayankt18]

/attempt #2195
using inquire

Options

• Cancel my attempt

[algora-pbc]

Note

The user @varshith257 is already attempting to complete issue #2195 and claim the bounty. We recommend checking in on @varshith257's progress, and potentially collaborating, before starting a new solution.

[dekkku]

/attempt #2195

Options

• Cancel my attempt

[algora-pbc]

@be-hunter: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏