Why selectors are part of the TemplateCacheKey?

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Why selectors are part of the TemplateCacheKey?

endSly
Hi all,

I'm implementing a custom TemplateResolver that relies on an external API to resolve the template content and using DOM selectors to split it into different parts. Calls to the external API are quite expensive, and, as I can see, the template resolver is called multiple times for the same template even though selectors are not included in the resolveTemplate method. What is the reason for this behavior?

Thanks!