It's easy to implement in UI-Library bindings. The new states (DebouncedState, ArrayFormState, ...) makes the way we do binding uncertain. After the binding pattern became clear in practices, we may add it back to formstate-x.
IState<V = any> -> IState<V = unknown>
Merge doValidation & applyValdiation (small refactoring for ValidatableState)
Explicit exports in src/index.ts
export * from './xxx' -> export { Foo, Bar } from './xxx'
Remove
isFormState
See details in https://github.com/qiniu/formstate-x/pull/37#discussion_r805230090
Remove
bindInput
It's easy to implement in UI-Library bindings. The new states (
DebouncedState
,ArrayFormState
, ...) makes the way we do binding uncertain. After the binding pattern became clear in practices, we may add it back to formstate-x.IState<V = any>
->IState<V = unknown>
Merge
doValidation
&applyValdiation
(small refactoring forValidatableState
)Explicit exports in
src/index.ts
export * from './xxx'
->export { Foo, Bar } from './xxx'
Remove
state.dispose()
in unit test cases