I opened the folder expecting spec file examples and found what the main ASF repo puts in a folder called example, would it make more sense to call it demo or example rather than test?

A standard best practise way to write jasmine tests could be included in a test folder instead perhaps.

If you have more js files they're all just being globbed by alphabetic order. This means that the "module" file can come after a directive or service and then you get no module errors.

I'd love that if there was an example/code in there where a directive was present and the sf-field-model was on that, would remove initial friction.

Ideally this would allow for multiple decorators, or even an option to add to all decorators, but that would require updates to the builder to support monitoring new decorators so that it could be added as new decorators are defined.

At the least being able to pick an alternate decorator would be an awesome start.

Hi,

I have:

yo (1.8.3)
npm (2.14.2)
node (v4.0.0)
ubuntu 14.04

I cannot easily upgrade the above since I have other projects depending on them.

When I run yo inside my add-on directory, I choose the add-on option and provide a name. Once I get to choose Input or Empty I get the error below:

TypeError: Cannot set property 'name' of undefined
    at null.<anonymous> (/usr/lib/node_modules/generator-angular-schema-form-add-on/app/index.js:48:23)
    at null.<anonymous> (/usr/lib/node_modules/generator-angular-schema-form-add-on/node_modules/yeoman-generator/lib/base.js:233:7)

Any help is greatly appreciated.

gulp minify creates a file called /dist/asf-addon.js, but /demo/index.html requests /dist/<addon-name>.js.

Right now we get the wrong type on $scope.form in test/index.html

This is because i've been stupid and totally forgot this was hardcoded.

Add more stuff to bower.json and package.json!

Test.html gets wrong prop and this should be myOwnFormOption!