ChainList

Good PR. But I think this method is starting to have too many arguments. Maybe a refactoring is necessary ?

Hi @bterrio, Today, we do not do any value equality in the code and we don't want to do so because it might be difficult for some edge cases (e.g...

Hi again @omer-g, Private life's been a bit busy recently. If you are willing to make a change and create a pull request it would be cool! otherwise i'm going...

Hi, I'm looking for a fix! Thanks for the report

FYIL @luist1228, The form being valid at first render is an expected behavior. As stated in the documentation on the `field` section:  When I change those options, it's seems...

Hi @eden-omb, Thanks for your PR. I'm currently reviewing what your changes imply for the rest of the code and futur improvements. I'll get back to you as soon as...

Hi @omer-g, Thanks a lot for all your feedbacks recently. The issues you pointed out about #50 are also the issues that I was worried about. cc: @eden-omb. Currently working...

Hi @eden-omb, Currently, `svelte-forms` takes dirty just as a "change" of value indeed. The meaning of the keyword carries this behavior. As for now, I currently don't think changing a...

To me setting a field as dirty is not quite what we want. We could do the same as Angular does with their forms: Adding a `touched` state. In addition...

Hi @omer-g, Indeed the documentation doesn't specifically point out that in case of a non numeric value (here: `string`) the validators consider the length of the value. I am going...