RC 1 release notes for field flags

So I was reading the release notes and saw this:

invalid -The field has been validated at least once and is not valid.

At least once, but that’s not correct, because when I don’t use v-validate.initial, the invalid=false and also valid=false

I feel like there is some inconsistency here. How is that invalid and valid are both false even though it says that the field should be validated at least once? It’s either implementation issue or a bad naming here.

The flags that I get initially without the ‘.initial’ are: { "untouched": true, "touched": false, "dirty": false, "pristine": true, "valid": false, "invalid": false } Which for me is confusing. Because you can use valid in one place and invalid on another and get totally different result.

[logaretm]

@twify93 I have added the null as the initial value for the valid and invalid flags, regarding the verbose conditions, the previous method API was somewhat neat but the flags wasn’t reactive meaning it caused a limited usage in computed props which was a critical thing to have. also there were a lot of inconsistencies between the flag behavior and the actual state of the input, so they had to be revised.

You can construct your own helpers for this, basically passes means that the field is dirty and is valid, so you can do that in your computed props, or use the included fieldsGetter which reduces the amount of conditions you have to write.

I might add the previous methods API via a similar helper. still have few more ways to improve this.

[logaretm]

I see, Null is a good value for undetermined status.