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

feat: Use Cappa by default #17

Open
pawamoy opened this issue Mar 20, 2024 · 1 comment
Open

feat: Use Cappa by default #17

pawamoy opened this issue Mar 20, 2024 · 1 comment
Assignees
Labels
feature New feature or request

Comments

@pawamoy
Copy link
Owner

pawamoy commented Mar 20, 2024

Cappa is 🔥

In some cases, the project will be CLI first, in that case there shouldn't be a cli extra.
But in other cases, the project will be library first, so we should probably put CLI dependencies (Cappa) behind a cli extra.

@pawamoy pawamoy added feature New feature or request fund Issue priority can be boosted labels Oct 25, 2024
@pawamoy pawamoy self-assigned this Jan 24, 2025
@pawamoy pawamoy added fund Issue priority can be boosted and removed fund Issue priority can be boosted labels Feb 19, 2025
@pawamoy pawamoy changed the title feat: Use Cappa by default, add question for an optional cli extra feat: Use Cappa by default Feb 19, 2025
@pawamoy
Copy link
Owner Author

pawamoy commented Feb 19, 2025

Nope, the way to handle CLI / no CLI is:

  • if you start with a lib, just create a regular project
  • if at some point you start offering a CLI, move code to a new projectlib, keep CLI in project
  • users can install project (full) or projectlib (minimal)
  • if you start a new project and know you will offer a CLI, create both project and projectlib

@pawamoy pawamoy removed the fund Issue priority can be boosted label Mar 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant