RetailCRM-Mirror/vue-formulario
1
0
Fork 0
mirror of synced 2024-11-22 05:16:05 +03:00
Code Issues Projects Releases Wiki Activity

fixes typos in the readme

Browse Source
This commit is contained in:
Luan Nguyen 2018-03-13 17:58:24 -05:00
parent c1e4b3948c
commit d85da177eb
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@ -114,17 +114,16 @@ in a `<formulate>` component. The `formulate` component has a single
required prop `name` which creates the form’s key in the vuex store.
All `formulate-element` components nested inside a `<formulate>`
component will automatically be commit mutations directly to the
component will automatically commit mutations directly to the
store. The store becomes a live representation of all your form’s
values.
The `formulate-element` component is a powerful component handles field
generation
The `formulate-element` component is a powerful component which handles field
generation.
### Validation Rules
There are several built in validation methods and you are easily able to add
your own.
There are several built-in validation methods and you can easily add your own as well.
Rule | Arguments
----------|---------------
@ -140,7 +139,7 @@ validation rules by using parenthesis after the rule name:
validation="required|confirmed(confirmation_field)"
```
The field label used in built in validation methods is the `validation-label`
The field label used in built-in validation methods is the `validation-label`
attribute on your `formulate-element`. If no `validation-label` is found then
the `label` attribute is used, and if no `label` attribute is found it will
fall back to the field’s `name` attribute (which is required).
@ -169,7 +168,7 @@ attribute on the `formulate-element`.
Validation rules should return an error message string if they failed, or
`false` if the input data is valid.
Adding your own validation rules is easy, just pass an additional object
Adding your own validation rules is easy. Just pass an additional object
of rule functions in the plugin’s installation call:
```js