Hennik Hunsaker

With fieldset support in place, we have an option for supporting subforms. I'll tackle dynamic add/remove (via updating the template, of course) after addressing #3, which should be relatively quick.

Yes, I haven't gotten that finished, yet. Hoping to sometime this weekend, though.

That's the hard part, and why it's not already in place. I really want to avoid changing anything in the DOM that doesn't need to be, but that means inspecting...

That's the plan, yes. The trick is keeping track of which DOM element corresponds with which template item. The code will need to be refactored some to make this work...

I hope to work on it some tomorrow, when I have time allocated to it. Hopefully nothing will come up to prevent that, like it has the past several weeks....

Continued apologies to everyone for not getting this done. I've had some trouble getting it to work properly, so some help would be appreciated. (I've also had some trouble finding...

Nothing to report beyond the "I don't have the time right now" in my previous comment. You may have better luck with one of the projects listed in the README...

Not currently. You might be able to simulate it by creating multiple controls with the same model (ngDynForms doesn't prevent you from doing that, by design). But nesting is not...

ID is an attribute just like any other, so just drop it in the `attributes` option. As for key-value pairs, maybe describing the option as an object would help... ```...

The plan is to support HTML templates instead of hard coded elements. It may be a little tricky to pull off properly, and the default templates should produce identical HTML...