I have two combos on a page one uses the loader: $.ig.loader('igCombo', function() {$('#MainMenuSearchCombo').igCombo the other does not $(function () {$('#BasicCriteriaReceiptIdType').igCombo(
Do you know what triggers using the loader vs not? Only 1 combo uses the loader and the rest don't and I can't figure out why that one is. I need it not to so any direction to point me in would be helpful.
I figured out why this is happening. Is there a way to tell it to ignore the loader?
Let me rephrase the question. When its using the igLoader its not seeing our custom template engine that we configured like this:
$.ig.tmpl = function (tmpl, data) {
var template = Handlebars.compile(tmpl);
return template(data);
};
Do you have to do something different with the template engine when the loader is used?
No it's in one of our own files. What is the recommendation for using the custom template with the loader. Where should we put the code to override it.
The igLoader loads the required IgniteUI resources. As you understand it will NOT load any other file. If you are referencing the file with the custom implementation explicitly, it seems like the igLoader loads the template engine later, thus overriding the $.ig.tmpl namespace with the original content. Considering this, try to load the custom implementation after the igLoader finishes its job and see if this makes any difference.
In any case, please provide a sample reproducing the issue, if any further assistance is needed.
Yeah I already tried that. I will see if I can reproduce it today our application is pretty complex. Do you guys have a recommendation for using the two together?
Also I tried this but still a no go...
$.ig.loader(function () {
configureIGTemplateEngine();
console.log('igGrid resources are loaded');
});
I got it to work. Thanks for your help!