This project is compatible with react-native ^0.9.0. I can't upgrade to react-native >= 0.10.0. If you need a more recent version, please fork the repo or submit a PR.
npm install tcomb-form-native
The tcomb library provides a concise but expressive way to define domain models in JavaScript.
The tcomb-validation library builds on tcomb, providing validation functions for tcomb domain models.
This library builds on those two and the awesome react-native.
With tcomb-form-native you simply call <Form type={Model} />
to generate a form based on that domain model. What does this get you?
- Write a lot less code
- Usability and accessibility for free (automatic labels, inline validation, etc)
- No need to update forms when domain model changes
JSON Schemas are also supported via the (tiny) tcomb-json-schema library.
The look and feel is customizable via react-native stylesheets and templates (see documentation).
http://react.rocks/example/tcomb-form-native
// index.ios.js
'use strict';
var React = require('react-native');
var t = require('tcomb-form-native');
var { AppRegistry, StyleSheet, Text, View, TouchableHighlight } = React;
var Form = t.form.Form;
// here we are: define your domain model
var Person = t.struct({
name: t.Str, // a required string
surname: t.maybe(t.Str), // an optional string
age: t.Num, // a required number
rememberMe: t.Bool // a boolean
});
var options = {}; // optional rendering options (see documentation)
var AwesomeProject = React.createClass({
onPress: function () {
// call getValue() to get the values of the form
var value = this.refs.form.getValue();
if (value) { // if validation fails, value will be null
console.log(value); // value here is an instance of Person
}
},
render: function() {
return (
<View style={styles.container}>
{/* display */}
<Form
ref="form"
type={Person}
options={options}
/>
<TouchableHighlight style={styles.button} onPress={this.onPress} underlayColor='#99d9f4'>
<Text style={styles.buttonText}>Save</Text>
</TouchableHighlight>
</View>
);
}
});
var styles = StyleSheet.create({
container: {
justifyContent: 'center',
marginTop: 50,
padding: 20,
backgroundColor: '#ffffff',
},
title: {
fontSize: 30,
alignSelf: 'center',
marginBottom: 30
},
buttonText: {
fontSize: 18,
color: 'white',
alignSelf: 'center'
},
button: {
height: 36,
backgroundColor: '#48BBEC',
borderColor: '#48BBEC',
borderWidth: 1,
borderRadius: 8,
marginBottom: 10,
alignSelf: 'stretch',
justifyContent: 'center'
}
});
AppRegistry.registerComponent('AwesomeProject', () => AwesomeProject);
Output:
(Labels are automatically generated)
Ouput after a validation error:
Returns null
if the validation failed, an instance of your model otherwise.
Note. Calling
getValue
will cause the validation of all the fields of the form, including some side effects like highlighting the errors.
Returns a ValidationResult
(see tcomb-validation for a reference documentation).
The Form
component behaves like a controlled component:
var Person = t.struct({
name: t.Str,
surname: t.maybe(t.Str)
});
var AwesomeProject = React.createClass({
getInitialState() {
return {
value: {
name: 'Giulio',
surname: 'Canti'
}
};
},
onChange(value) {
this.setState({value});
},
onPress: function () {
var value = this.refs.form.getValue();
if (value) {
console.log(value);
}
},
render: function() {
return (
<View style={styles.container}>
<Form
ref="form"
type={Person}
value={this.state.value}
onChange={this.onChange}
/>
<TouchableHighlight style={styles.button} onPress={this.onPress} underlayColor='#99d9f4'>
<Text style={styles.buttonText}>Save</Text>
</TouchableHighlight>
</View>
);
}
});
The onChange
handler has the following signature:
(raw: any, path: Array<string | number>) => void
where
raw
contains the current raw value of the form (can be an invalid value for your model)path
is the path to the field triggering the change
Warning. tcomb-form-native uses
shouldComponentUpdate
aggressively. In order to ensure that tcomb-form-native detect any change totype
,options
orvalue
props you have to change references:
var Type = t.struct({
disable: t.Bool, // if true, name field will be disabled
name: t.Str
});
// see the "Rendering options" section in this guide
var options = {
fields: {
name: {}
}
};
var AwesomeProject = React.createClass({
getInitialState() {
return {
options: options,
value: null
};
},
onChange(value) {
// tcomb immutability helpers
// https://github.com/gcanti/tcomb/blob/master/GUIDE.md#updating-immutable-instances
var options = t.update(this.state.options, {
fields: {
name: {
editable: {'$set': !value.disable}
}
}
});
this.setState({options: options, value: value});
},
onPress: function () {
var value = this.refs.form.getValue();
if (value) {
console.log(value);
}
},
render: function() {
return (
<View style={styles.container}>
<Form
ref="form"
type={Type}
options={this.state.options}
value={this.state.value}
onChange={this.onChange}
/>
<TouchableHighlight style={styles.button} onPress={this.onPress} underlayColor='#99d9f4'>
<Text style={styles.buttonText}>Save</Text>
</TouchableHighlight>
</View>
);
}
});
You can get access to a field with the getComponent(path)
API:
var Person = t.struct({
name: t.Str,
surname: t.maybe(t.Str),
age: t.Num,
rememberMe: t.Bool
});
var AwesomeProject = React.createClass({
componentDidMount() {
// give focus to the name textbox
this.refs.form.getComponent('name').refs.input.focus();
},
onPress: function () {
var value = this.refs.form.getValue();
if (value) {
console.log(value);
}
},
render: function() {
return (
<View style={styles.container}>
<Form
ref="form"
type={Person}
/>
<TouchableHighlight style={styles.button} onPress={this.onPress} underlayColor='#99d9f4'>
<Text style={styles.buttonText}>Save</Text>
</TouchableHighlight>
</View>
);
}
});
By default fields are required:
var Person = t.struct({
name: t.Str, // a required string
surname: t.Str // a required string
});
In order to create an optional field, wrap the field type with the t.maybe
combinator:
var Person = t.struct({
name: t.Str,
surname: t.Str,
email: t.maybe(t.Str) // an optional string
});
The postfix " (optional)"
is automatically added to optional fields.
You can customise the postfix value or setting a postfix for required fields:
t.form.Form.i18n = {
optional: '',
required: ' (required)' // inverting the behaviour: adding a postfix to the required fields
};
In order to create a numeric field, use the t.Num
type:
var Person = t.struct({
name: t.Str,
surname: t.Str,
email: t.maybe(t.Str),
age: t.Num // a numeric field
});
tcomb-form-native will convert automatically numbers to / from strings.
In order to create a boolean field, use the t.Bool
type:
var Person = t.struct({
name: t.Str,
surname: t.Str,
email: t.maybe(t.Str),
age: t.Num,
rememberMe: t.Bool // a boolean field
});
Booleans are displayed as SwitchIOS
s.
In order to create a date field, use the t.Dat
type:
var Person = t.struct({
name: t.Str,
surname: t.Str,
email: t.maybe(t.Str),
age: t.Num,
birthDate: t.Dat // a date field
});
Dates are displayed as DatePickerIOS
s.
In order to create an enum field, use the t.enums
combinator:
var Gender = t.enums({
M: 'Male',
F: 'Female'
});
var Person = t.struct({
name: t.Str,
surname: t.Str,
email: t.maybe(t.Str),
age: t.Num,
rememberMe: t.Bool,
gender: Gender // enum
});
Enums are displayed as PickerIOS
s.
A predicate is a function with the following signature:
(x: any) => boolean
You can refine a type with the t.subtype(type, predicate)
combinator:
// a type representing positive numbers
var Positive = t.subtype(t.Num, function (n) {
return n >= 0;
});
var Person = t.struct({
name: t.Str,
surname: t.Str,
email: t.maybe(t.Str),
age: Positive, // refinement
rememberMe: t.Bool,
gender: Gender
});
Subtypes allow you to express any custom validation with a simple predicate.
In order to customize the look and feel, use an options
prop:
<Form type={Model} options={options} />
By default labels are automatically generated. You can turn off this behaviour or override the default labels on field basis.
In order to automatically generate default placeholders, use the option auto: 'placeholders'
:
var options = {
auto: 'placeholders'
};
<Form type={Person} options={options} />
Set auto: 'none'
if you don't want neither labels nor placeholders.
var options = {
auto: 'none'
};
You can sort the fields with the order
option:
var options = {
order: ['name', 'surname', 'rememberMe', 'gender', 'age', 'email']
};
You can set the default values passing a value
prop to the Form
component:
var value = {
name: 'Giulio',
surname: 'Canti',
age: 41,
gender: 'M'
};
<Form type={Model} value={value} />
You can configure each field with the fields
option:
var options = {
fields: {
name: {
// name field configuration here..
},
surname: {
// surname field configuration here..
}
}
});
Implementation: TextInput
Tech note. Values containing only white spaces are converted to null
.
You can set the placeholder with the placeholder
option:
var options = {
fields: {
name: {
placeholder: 'Your placeholder here'
}
}
};
You can set the label with the label
option:
var options = {
fields: {
name: {
label: 'Insert your name'
}
}
};
You can set a help message with the help
option:
var options = {
fields: {
name: {
help: 'Your help message here'
}
}
};
You can set a custom error message with the error
option:
var options = {
fields: {
email: {
error: 'Insert a valid email'
}
}
};
tcomb-form-native will show the error message when the field validation fails. You can also use a function with the following signature:
(value: any) => string
where the value
param contains the current field value. The value returned by the function will be used as message.
The following standard options are available (see http://facebook.github.io/react-native/docs/textinput.html):
autoCapitalize
autoCorrect
autoFocus
bufferDelay
clearButtonMode
editable
enablesReturnKeyAutomatically
keyboardType
multiline
onBlur
onEndEditing
onFocus
onSubmitEditing
password
placeholderTextColor
returnKeyType
selectTextOnFocus
secureTextEntry
selectionState
Implementation: SwitchIOS
The following options are similar to the Textbox
component's ones:
label
help
error
The following standard options are available (see http://facebook.github.io/react-native/docs/switchios.html):
disabled
onTintColor
thumbTintColor
tintColor
Implementation: PickerIOS
The following options are similar to the Textbox
component's ones:
label
help
error
You can customize the null option with the nullOption
option:
var options = {
fields: {
gender: {
nullOption: {value: '', label: 'Choose your gender'}
}
}
};
You can remove the null option setting the nullOption
option to false
.
Warning: when you set nullOption = false
you must also set the Form's value
prop for the select field.
Tech note. A value equal to nullOption.value
(default ''
) is converted to null
.
You can sort the options with the order
option:
var options = {
fields: {
gender: {
order: 'asc' // or 'desc'
}
}
};
Implementation: DatePickerIOS
var Person = t.struct({
name: t.Str,
birthDate: t.Dat
});
The following options are similar to the Textbox
component's ones:
label
help
error
The following standard options are available (see http://facebook.github.io/react-native/docs/datepickerios.html):
maximumDate
,minimumDate
,minuteInterval
,mode
,timeZoneOffsetInMinutes
tcomb-form-native comes with a default style. You can customize the look and feel by setting another stylesheet:
var t = require('tcomb-form-native');
// define a stylesheet (see lib/stylesheets/bootstrap for an example)
var stylesheet = {...};
// override globally the default stylesheet
t.form.Form.stylesheet = stylesheet;
You can also override the stylesheet locally:
var Person = t.struct({
name: t.Str
});
var options = {
fields: {
name: {
stylesheet: myCustomStylesheet
}
}
};
For a complete example see the default stylesheet https://github.com/gcanti/tcomb-form-native/blob/master/lib/stylesheets/bootstrap.js.
tcomb-form-native comes with a default layout, i.e. a bunch of templates, one for each component. When changing the stylesheet is not enough, you can customize the layout by setting custom templates:
var t = require('tcomb-form-native');
// define the templates (see lib/templates/bootstrap for an example)
var templates = {...};
// override globally the default layout
t.form.Form.templates = templates;
You can also override the template locally:
var Person = t.struct({
name: t.Str
});
function myCustomTemplate(locals) {
var containerStyle = {...};
var labelStyle = {...};
var textboxStyle = {...};
return (
<View style={containerStyle}>
<Text style={labelStyle}>{locals.label}</Text>
<TextInput style={textboxStyle} />
</View>
);
}
var options = {
fields: {
name: {
template: myCustomTemplate
}
}
};
A template is a function with the following signature:
(locals: Object) => ReactElement
where locals
is an object contaning the "recipe" for rendering the input and it's built for you by tcomb-form-native.
Let's see an example: the locals
object passed in the checkbox
template:
{
stylesheet: Object, // the styles to be applied
hasError: boolean, // true if there is a validation error
error: ?string, // the optional error message to be displayed
label: string, // the label to be displayed
help: ?string, // the optional help message to be displayed
value: boolean, // the current value of the checkbox
onChange: Function, // the event handler to be called when the value changes
...other input options here...
}
For a complete example see the default template https://github.com/gcanti/tcomb-form-native/blob/master/lib/templates/bootstrap.js.
Say you want a search textbox which accepts a list of keywords separated by spaces:
var Search = t.struct({
search: t.list(t.Str)
});
tcomb-form by default will render the search
field as a list. In order to render a textbox you have to override the default behaviour with the factory option:
var options = {
fields: {
search: {
factory: t.form.Textbox
}
}
};
There is a problem though: a textbox handle only strings so we need a way to transform a list in a string and a string in a list: a Transformer
deals with serialization / deserialization of data and has the following interface:
var Transformer = t.struct({
format: t.Func, // from value to string, it must be idempotent
parse: t.Func // from string to value
});
A basic transformer implementation for the search textbox:
var listTransformer = {
format: function (value) {
return Array.isArray(value) ? value.join(' ') : value;
},
parse: function (str) {
return str ? str.split(' ') : [];
}
};
Now you can handle lists using the transformer option:
// example of initial value
var value = {
search: ['climbing', 'yosemite']
};
var options = {
fields: {
search: {
factory: t.form.Textbox, // tell tcomb-react-native to use the same component for textboxes
transformer: listTransformer,
help: 'Keywords are separated by spaces'
}
}
};
You can pack together style, template (and transformers) in a custom component and then you can use it with the factory
option:
var Component = t.form.Component;
// extend the base Component
class MyComponent extends Component {
// this is the only required method to implement
getTemplate() {
// define here your custom template
return function (locals) {
//return ... jsx ...
};
}
// you can optionally override the default getLocals method
// it will provide the locals param to your template
getLocals() {
// in locals you'll find the default locals:
// - path
// - error
// - hasError
// - label
// - onChange
// - stylesheet
var locals = super.getLocals();
// add here your custom locals
return locals;
}
}
// as example of transformer: this is the default transformer for textboxes
MyComponent.transformer = {
format: value => Nil.is(value) ? null : value,
parse: value => (t.Str.is(value) && value.trim() === '') || Nil.is(value) ? null : value
};
var Person = t.struct({
name: t.Str
});
var options = {
fields: {
name: {
factory: MyComponent
}
}
};
npm test
MIT