Enhance tailcall init
Command for Improved Developer Experience
#3135
Labels
state: inactive
No current action needed/possible; issue fixed, out of scope, or superseded.
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:Auto-detection of Configuration Format:
.tailcallrc.graphql
or.tailcallrc.yaml
).Example Improvement:
Instead of showing:
Automatically infer the format from the existing file.
Skip Confirmation for Overwriting
.tailcallrc
:.tailcallrc
file should not require user confirmation, as it is mandatory for IDEs to understand the Tailcall configuration.Current Behavior:
Proposed Change: Automatically overwrite the file without prompting.
Skip Overwriting
main.graphql
: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:
tailcall init
in an existing Tailcall project directory.The text was updated successfully, but these errors were encountered: