@zecos/fieldz v0.0.8
fieldz
fieldz is a form state management tool that should integrate well with
It's a minimalistic library with only ~90 LoC and follows functional programming pattern.
It's also heckin' easy to use.
The first step is to declare your field properties:
import { nameValidator } from "validatorz"
const fieldProperties = {
firstName: {
init: "",
validate: nameValidator
},
customField: {
validate: (val: string) => {
if (val !== "hello") {
return [new Error("value must be hello!")]
}
return []
},
init: "this is my init value"
}
}Field properties consist of two values:
init: initial value for the fieldvalidate: validation function that returns array of errors
This library is designed to integrate well with validatorz,
but you can feel free to use whatever validation functions you want like in customField.
Next, we instantiate our fieldz™ using the fieldz function:
import { fields } from 'fieldz'
// fieldProperties
const { getState } = fields(fieldProperties)
const state = getState()You can see fields returns a function called getState.
getState does just what it sounds like: gets state.
state is the initial state of our fields. It's just data.
For our field properties, it would be something like this:
{
firstName: {
errors: [],
touched: false,
pristine: true,
value: ''
},
customField: {
errors: [],
touched: false,
pristine: true,
value: 'this is my init value'
}
}There are 4 state properties
errors: their array of errors (possibly empty) based on the current valuevalue: their current valuetouched: boolean: whether they have been "touched" or not (the value has been adjusted, and theinputhas lost focus)pristine: a boolean value indicating whether or not the fields have been
Quite simple, but how do we manipulate state?
Well, for that, we'll turn to our actions:
const { getState, ...actions } = fields(fieldProperties)
const { setValue, setValues, setTouched, resetField, resetFields, setState } = actionsEach action adjusts state and then returns the new state:
setValue:- takes a
keyand avalue - validates the data sets
errorsto any returned errors from the validator - sets pristine to
falseif not already set
- takes a
setValues:- takes a map of key values
- performs everything
setValuedoes
setTouched: sets field'stouchedproperty to true if not already setresetField: sets a field's properties to their original valueresetFields: same asresetField, but for all fieldssetState:- sets the internal
fieldsstate - hopefully, you'll never need this
- sets the internal
But enough of the theory, let's see it in action.
With large chunks of code omitted, you could see something like this:
import { fields } from 'fieldz'
import { nameValidator } from "validatorz"
const fieldProperties = {
firstName: {
errors: [],
touched: false,
pristine: true,
value: ''
},
customField: {
errors: [],
touched: false,
pristine: true,
value: 'this is my init value'
}
}
const Form = () => {
const [[actions, formState], _setFormState] = useState(() => fields(fieldProperties))
const { setValue, setValues, setTouched, resetField, resetFields, setState } = actions
const setFormState = state => _setFormState([actions, state])
return (
<form>
{Object.entries(formState)
.map(([fieldName, {errors, value, touched, pristine}]) => (
<div>
{(touched && errors.length) ? <span className="input-error">{errors.map(err => <div>{err.toString()}</div>)}</span> : ""}
<label for={fieldName}>{camelToTitle(fieldName)}</label>
<input
name={fieldName}
value={value}
onChange={e => setFormState(setValue(fieldName, e.target.value))}
onBlur={_ => setFormState(setTouched(fieldName))}
/>
</div>
))
}
</form>
)
}This is made much easier now with react-fieldz, so be sure to check that out.
In addition, you can now just import one field by using the field function, like so:
import { field } from 'fieldz'
import { nameValidator } from 'validatorz'
const firstName = field({
init: "",
validator: nameValidator,
})