@@ -109,7 +109,7 @@ It takes the form definition as an argument.
109
109
| schemaError() | The current error object from tv4js |
110
110
111
111
112
- ### Setting up schema defualts
112
+ ### Setting up schema defaults
113
113
So you got this shiny new add-on that adds a fancy field type, but feel a bit bummed out that you
114
114
need to specify it in the form definition all the time? Fear not because you can also add a "rule"
115
115
to map certain types and conditions in the schema to default to your type.
@@ -149,6 +149,19 @@ var datepicker = function(name, schema, options) {
149
149
schemaFormProvider .defaults .string .unshift (datepicker);
150
150
```
151
151
152
+ ### Sharing your add-on with the world
153
+ So you made an add-on, why not share it with us? On the front page,
154
+ [ http://textalk.github.io/angular-schema-form/ ] ( http://textalk.github.io/angular-schema-form/ ) , we
155
+ maintain a list of add ons based on a query of the bower register, and we love to see your add-on
156
+ there.
157
+
158
+ Any [ bower] ( http://bower.io ) package with a name starting with ` angular-schema-form- ` or that has
159
+ the ` keyword ` ` angular-schema-form-add-on ` in its ` bower.json ` will be picked up. It's cached so
160
+ there can be a delay of a day or so.
161
+
162
+ So [ make a bower package] ( http://bower.io/docs/creating-packages/ ) , add the keyword
163
+ ` angular-schema-form-add-on ` and [ register it] ( http://bower.io/docs/creating-packages/#register ) !
164
+
152
165
Decorators
153
166
----------
154
167
Decorators are a second way to extend Schema Form, the thought being that you should easily be able
0 commit comments