The move to template-url disallows the use of scoped values about angular-cron-gen

[icfantv]

There's an ugly way (read: hack) of using $templateCache to resolve this issue when using webpack's require and a template loader:

.run($templateCache => $templateCache.put('some-string', $templateCache.get(require('path/to/template.html')));

And then use some-string as the value of your template-url attribute.

It's ugly because you have the same entry in your cache twice.

[vincentjames501]

Nice. To be honest I haven't done much testing with loading another template. Do you have any suggestions?

[icfantv]

I'm in the process of updating our template to account for all the changes from 0.0.6 (where there was a bug we just found about the hourly regex check was incorrectly matching a daily cron expression). I can link this issue in to my PR in our project when I have it done so you can see what we wound up doing.

[icfantv]

@vincentjames501 here's the PR for our project utilizing a custom template.

[vincentjames501]

@icfantv , would you be willing to update the README with a PR and document how you did it?

[icfantv]

@vincentjames501 yea, but it's not straightforward. i had to look at your demo and the classes themselves to see what was exposed to put into a custom template. if you were to document your classes that might make it a lot easier.