Skip to content

[CLI] Improve Init Command #129

@cstrnt

Description

@cstrnt

Problem
The current initcommand 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/DX

Solution:
The init command should provide a full hands-on experience. The shadcn CLI is a great example of that (reference).

Potential Workflow:

  1. User runs Abby init
  2. Ask for the location (should default to the current dir)
  3. If there is an abby.config.ts warn the user and abort.
  4. Get a list of all projects available for the signed-in user
  5. Show the user a list of all projects (select)
  6. Let the user select a project
  7. Fetch all existing items for the current project (environments, flags, remote configs, tests)
  8. Show the user an overview of the config that will be written to the file
  9. Allow the user to accept or cancel

Acceptance Criteria:

  • User errors are caught and displayed in a nice manner
  • the currentEnvironment field should be set to process.env.NODE_ENV by default
  • all existing data must be set for the projects

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions