Trying to generate default output Using External Config about angularagility

[johnculviner]

Hi @randallmeeker, good question. I actually took the external config stuff as a pull from @rolandzwaga and haven't personally tried it yet. It should be working though. I'd love it if you'd find it out and update the docs in a pull with some more examples as I think that sort of functionality is very useful!

[randallmeeker]

So far as I can tell it works for validations only. and does not work with wrapping in markup. In order to wrap in mark up I have to use aa-field-group, but in order to use external config I have to use ng-model. So their not really compatible. I should have time to play with it some more.

[johnculviner]

Interesting, yeah keep me posted as you dig in more and lets try to make it as useful as possible for everyone!

[rolandzwaga]

hey sorry for the late reply. Indeed, the external config won't work with aa-field or aa-field-group. Because, indeed (again), the external config uses the ng-model value to look up its validation info. (aa-label and stuff does work though.)
The issue is a chicken and egg problem, when the external config parses the HTML, it isn't compiled yet, so the aa-field and aa-field-group directives haven't done their magic yet, so there's no ng-model to be found on these elements.
Perhaps I could build in a check specifically for aa-field and aa-field-group attributes and use their values for the validation lookup.
I'll have a look into this once I find some time.

cheers,

Roland

[rolandzwaga]

ok, so I did a check test and it actually seems to work, just had to add one line of code...
Here's the PR: #53
Like I say, it was a quick fix, without a huge testing effort, so there might be some residual issues, but AFAICS this works the way its supposed to.

cheers.

[johnculviner]

Sweet