Skip to content

feat: add number prompt, fix note component, change directory structure, add feature to multiselect prompt #352

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

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

hyperz111
Copy link

feat: add number prompt, fix note component, change directory structure, add feature to multiselect prompt

Note

I CANNOT install biome

What's Changes?

  1. Add number prompt to @clack/prompts.
  2. Change directory structure of @clack/prompts (opinionated).
  3. Fix note component overflow glitch.
  4. Add toggle invert for multiselect prompt by press i key.
  5. Add toggle all & invert for group-multiselect prompt.
  6. Add sisteransi and picocolors as devDependencies, it's mean bundling (it's works).
  7. Add wrap-ansi.
  8. And other....

Copy link

changeset-bot bot commented Jul 7, 2025

🦋 Changeset detected

Latest commit: 5dac824

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@clack/core Minor
@clack/prompts Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@43081j
Copy link
Collaborator

43081j commented Jul 7, 2025

individually, most of these changes are probably fine, but they need splitting up into separate changes, separate PRs.

repo-level changes, like the structure, also need to be agreed by the team. so would be better as an issue rather than a PR for now

some of what you've changed are bug fixes and should be fixed. others are features we need discussion around to decide if we even want such a feature

if you open individual PRs, we can discuss in the PRs

@hyperz111
Copy link
Author

individually, most of these changes are probably fine, but they need splitting up into separate changes, separate PRs.

repo-level changes, like the structure, also need to be agreed by the team. so would be better as an issue rather than a PR for now

some of what you've changed are bug fixes and should be fixed. others are features we need discussion around to decide if we even want such a feature

if you open individual PRs, we can discuss in the PRs

Hmm ok thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants