If you have: experience-cloud/components/myComponent
that extends: dexter/components/myComponent and you attempt to call: experience-cloud/components/myComponent/myTemplate.html when that file only exists in the resourceSuperType. Sling / HTL will kindly let you know that resource does not exist. My question is; is this the desired result? What's interesting is that HTL data-sly-call *does* respect certain base Sling features like resourceResolver resolution fallbacks of /apps -> /libs. But it doesn't support this other use case. While I think the current Impl makes sense, I could see scenarios where it might not for others. It does create more duplicate code because someone who extends will absolutely have to write that file to the JCR. Thoughts? Chris
