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(input): Skip validation when going to previous field #285

Merged
merged 3 commits into from
Nov 27, 2024

Conversation

Sculas
Copy link
Contributor

@Sculas Sculas commented Jun 18, 2024

In my opinion, this would make user experience better. Say you made a typo in the previous field but you already went to the next one, now you need to fill the current field correctly before you can fix the previous field.

This also keeps validation intact, because the field still needs to be valid to progress to the next field.

In my opinion, this would make user experience better. Say you made a typo in the previous field but you already went to the next one, now you *need* to fill the current field correctly before you can fix the previous field.

This also keeps validation intact, because the field still needs to be valid to progress to the next field.
@Sculas Sculas requested a review from maaslalani as a code owner June 18, 2024 23:40
@caarlos0 caarlos0 changed the title refactor(input): Skip validation when going to previous field feat(input): Skip validation when going to previous field Jul 25, 2024
@caarlos0 caarlos0 merged commit aad810d into charmbracelet:main Nov 27, 2024
20 checks passed
@caarlos0
Copy link
Member

Thanks!

@Sculas Sculas deleted the refactor/skip-prev-validation branch November 27, 2024 14:49
jonas-grgt pushed a commit to jonas-grgt/huh that referenced this pull request Jan 28, 2025
…et#285)

In my opinion, this would make user experience better. Say you made a typo in the previous field but you already went to the next one, now you *need* to fill the current field correctly before you can fix the previous field.

This also keeps validation intact, because the field still needs to be valid to progress to the next field.
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