-
Notifications
You must be signed in to change notification settings - Fork 16
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
[CLI] Improve Init Command #129
Labels
good first issue
Good for newcomers
Comments
Hi @cstrnt, I'll love to contribute. Can you assign this to me? |
@Ekep-Obasi Sure thing! Thank you so much :) Feel free to always ask questions if you need help or join our Discord |
Hey @Ekep-Obasi Is there anything you need assistance with? |
@cstrnt , I've pinged you on discord |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
The current
init
command is quite basic and doesn't provide much value. It requires a lot of manual work and doesn't align with Abby's level of UX/DXSolution:
The
init
command should provide a full hands-on experience. The shadcn CLI is a great example of that (reference).Potential Workflow:
abby.config.ts
warn the user and abort.Acceptance Criteria:
currentEnvironment
field should be set toprocess.env.NODE_ENV
by defaultThe text was updated successfully, but these errors were encountered: