Dirty tracking doesn't work without setting initial form values.

[genu]

Describe the bug
Related discussion: #126 (comment)

To Reproduce
This bug can be seen when checking the isDirty() of a form when it doesn't have initialValues. It will always be true

Expected behavior
Form should only be dirty when fields are modified.

[logaretm]

Looks like having any sort of nested fields (grouped or not) causes this bug to happen, top level fields work as expected.

This is because when a field is nested it creates a nested path in the form values, where in a top-level field, the initialization is skipped then.

This can still happen if the initial values didn't contain that nested path, so it would initialize itself and would then cause the dirty check to be buggy.

I'm thinking about how to approach this, but setting the original values on field init transaction is dangerous because it may not be the result of a first render, it could be a toggled field (v-if) or managed by a field repeater 🤔

Maybe instead, the dirty status should be tracked like how touched is being tracked. Manually.

[genu]

Thanks for the thorough explanation @logaretm

I'll test the PR on my end.