nzdeep

Bug with Transitions Show vs {cond && <Comp/>}

2

### Describe the bug Adding this here just so it doesn't get missed in 2.0 or 2.x milestone if we're beyond 2.0 planning already, understand things are hectic with transition...

custom validators need some context, any context

5

A custom validator - that is to be re-usable - needs some context? what path is it operating on at minimum? the definition of the field (the field props)? the...

more critical bugs - this time getvalue on object

10

https://playground.solidjs.com/anonymous/4221f2ef-06b4-46da-9594-a8c1caabc357 This is very dangerous, returns old values 1) Click mutate 2) Click 'show' 3) Expect 'def' get 'abc' Reached the point where we rapidly loosing confidence in any correctness.

More bugs with getValues

3

https://playground.solidjs.com/anonymous/02fc8d25-3447-49b5-b245-8059618a1194 Should show ```{x: "hello"}````

defaultFilters

1

Enhancement idea: FormOptions should have a defaultFilters options ``` createFormStore({ defaultFilters: { shouldActive : false } }) ```

dirty tracking

3

It's not clear to me why when initialValues re-seed matches the current state is dirty still true if it matches the reseeding. So even though we keepDirtyValues, if dirty values...