feat: rework values and user input to be separate

[43081j]

Fixes #330

Basically, this introduces a new userInput field and event to the core.

The difference is:

• userInput tracks what the user has typed in (if track: true)
• nothing changes value in the core anymore

This means it is the responsibility of each prompt to decide what to do with value. They can then call this._setValue(value) to set the value and trigger the value event.

An example - text prompt

The text prompt wants to set the value to what the user has typed in. So we can simply listen for userInput and set value to whatever they have typed. Or we can wait for finalize and do it.

A more complex example - auto complete

The auto complete prompt wants to take user input, but this isn't the value. The value should be the completed value.

To achieve this, we can set value only once someone selects an option.

This means the value is only ever undefined or a selected option.

Notable changes

• Validation only occurs when you submit (press <RETURN>), it used to run against initial values too
• Validation can receive undefined (it always could but we didn't type it as such, iirc)
• Validation function is strongly typed (i.e. it takes value as a strong type)

[changeset-bot]

🦋 Changeset detected

Latest commit: 831029d

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

This PR includes changesets to release 2 packages

Name	Type
@clack/prompts	Minor
@clack/core	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

[pkg-pr-new]

@example/basic • @example/changesets

npm i https://pkg.pr.new/bombshell-dev/clack/@clack/core@334

npm i https://pkg.pr.new/bombshell-dev/clack/@clack/prompts@334

commit: 831029d

[dreyfus92]

i really like this refactor, you're just lacking a changeset and i'm wondering if these changes impact all the examples we've created in the examples dir

[dreyfus92]

Let's ship it 🫡