Awesome research @jmooring !
We pretty much exclusively use partialCached
so it didn’t occur to me that partial
is handled differently.
For the original caching/metrics question… Adding the extension does fix it but does this mean that when you don’t use the extension with partialCached, aka, {{ partialCached "bar" . }}
instead of with the extension aka {{ partialCached "bar.html" . }}
that templateMetrics reporting considers them separately or that it’s not caching properly?
Also, for what it’s worth. in the test repo there isn’t inconsistent usage when specifying the template name but it’s still happening.
Is it a requirement to include the extension when using partial
and partialCached
?
I also never thought about or noticed that the docs use the extension when using partial
or partialCached
. Is it an incorrect usage to not include the .html
extension?
This post from 2017 suggests that not including the extension with any partial call is incorrect:
Thanks in advance! I’m betting every larger Hugo site relies on partialCached
and --templateMetrics
so hopefully your efforts also help many other users/sites!