Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance tailcall init Command for Improved Developer Experience #3135

Open
amitksingh1490 opened this issue Nov 20, 2024 · 2 comments · May be fixed by #3146
Open

Enhance tailcall init Command for Improved Developer Experience #3135

amitksingh1490 opened this issue Nov 20, 2024 · 2 comments · May be fixed by #3146
Assignees
Labels
state: inactive No current action needed/possible; issue fixed, out of scope, or superseded.

Comments

@amitksingh1490
Copy link
Collaborator

amitksingh1490 commented Nov 20, 2024

Description:

Currently, the tailcall init command is not optimized for reinitializing a Tailcall project after updating the Tailcall version. This process can be made more seamless with the following enhancements:

  1. Auto-detection of Configuration Format:

    • When reinitializing a project, the command should automatically detect the configuration format (GraphQL/YAML) based on existing files in the folder (e.g., .tailcallrc.graphql or .tailcallrc.yaml).
    • Only prompt the user to choose a format if no configuration file is detected.

    Example Improvement:
    Instead of showing:
    image
    Automatically infer the format from the existing file.

  2. Skip Confirmation for Overwriting .tailcallrc:

    • Overwriting the .tailcallrc file should not require user confirmation, as it is mandatory for IDEs to understand the Tailcall configuration.

    Current Behavior:
    image
    Proposed Change: Automatically overwrite the file without prompting.

  3. Skip Overwriting main.graphql:

    • Reinitializing should not overwrite main.graphql

    Current Behavior:

    main.graphql already exists. Overwrite? (y/n)  

    Proposed Change: don't overwrite main.graphql.

These changes will improve the developer experience by reducing unnecessary steps and making the tailcall init command more intuitive during reinitialization.


Steps to Reproduce Current Behavior:

  1. Run tailcall init in an existing Tailcall project directory.
  2. Observe the prompts for configuration format and confirmation to overwrite files.
@webbdays
Copy link
Contributor

webbdays commented Nov 22, 2024

Hi,
these commands like

tailcall update
or
tailcall schema update/upgrade

isnt enough?
this looks nice.

@karatakis karatakis self-assigned this Nov 25, 2024
@karatakis karatakis linked a pull request Nov 25, 2024 that will close this issue
6 tasks
Copy link

Action required: Issue inactive for 30 days.
Status update or closure in 7 days.

@github-actions github-actions bot added the state: inactive No current action needed/possible; issue fixed, out of scope, or superseded. label Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state: inactive No current action needed/possible; issue fixed, out of scope, or superseded.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants