🦋 Changeset detected

Latest commit: bdedd6e

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

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

Just tested it, works great for me! 👍

Sorry for asking here about the status again - we're desperately waiting for this feature and this pr has been unreviewed for almost 2 weeks now 🤷‍♂️

Is there anything that can be done to help get this reviewed soon(ish)? Thanks in advance!

@LeeWxx do you think, you can request a review from maintainers?

@hrueger I don’t think I have permission to request reviewers either.
Do you happen to know if there’s any other way to get this reviewed?

Very strange... I usually don't tag random people as I've heard it is considered rude. So hopefully Mr Svelte himself (aka @Rich-Harris) sees this as a friendly request for review? 😃🙏 thanks in advance!

I think it would be beneficial to differentiate (and individually support) both touched and dirty state for form fields, where the former checks for any modification from the original state (and remains touched once any modification occurs), and the latter keeps track of difference from original and current form state (where dirty would be false if all form fields are the same as original, even if touched is true).

Ideally, I'd want to implement the following behavior:

• I have a field, which can be plain, or outlined green or outlined red with a list of issues
• at the beginning, the field is plain / idle
• When the user types and the validation passes, it becomes green
• when the user types more or removes chats so that the field becomes invalid, it should become red and the issue list should display
• or when the user does not input valid content and the field is blurred, then it should become red

Note that when inputting for the first time, it only can become red after it was already green. So that you don't confuse the user with a min length issue for example while he is still typing.

Does that make sense? Hard to express in writing 😁

Would that be possible without manually keeping track of the validation success of each field? Maybe we need a blurredOnce tracker, too? Not sure.

@LeeWxx I think a good place would be the contributors channel in the svelte discord.

@firatciftci @hrueger I started with adding support for the touched state only in this PR to keep the scope small and focused. Once we agree on the purpose and desired behavior in the issue or discussion, I’m thinking of following up with another PR for dirty and related states. Would that make sense to you?