Hennik Hunsaker

I'm not sure why that's not working... One thing to note is that the `required` key creates an `ng-required` attribute on the form element, so the value there needs to...

Well, it looks like you've used `name` in a couple of places instead of `model`. Also, spaces aren't a great idea in model names, so I'd avoid using them in...

Not at the moment, no. There's a plan to add HTML templates for each control, with full support for overriding them, but that hasn't been implemented, yet.

That's certainly unusual. I can't say I'm able to reproduce this one, but since this module simply generates standard input tags, then lets Angular take over, I'm fairly confident the...

All of those features are handled by Angular already, so rather than reinventing the wheel, I simply have Angular handle them as usual. The README references the Angular docs often...

Add the `style` key under `attributes`. As to the order, forms are built in the order they're defined in the JSON, at the moment.

I'm not aware of any reason for that not to work. Can you provide more detail on the error, and some sample code that generates it?

The same way you would any Angular project. The validation rules themselves are already directly supported, to the extent that HTML5 and core Angular define them. Neither natively supports error...

Not familiar with ng-grid, so I don't have any specific advice here.

It should already have dynamic element add/remove, as that was one of my design goals starting out, but I don't recall testing it... This is indeed essential. As for subforms,...