fix bug in picture with params

[stereobooster]

I found a bug in implementation. Apparently $.Page.Site.Params... always evaluates to undefined in the context of picture.html. One way to fix it is always pass params explicitly. Other way would be to pass .Page, I guess

[netlify]

✅ Deploy Preview for hugo-congo ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	f2af019
🔍 Latest deploy log	https://app.netlify.com/sites/hugo-congo/deploys/656742871b3342000817a131
😎 Deploy Preview	https://deploy-preview-730--hugo-congo.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[wolfspyre]

is it “better” to eval the current page’s params context as well for $lazy?
thus enabling it to be configurable per page?

i honestly dunno.. just asking

[stereobooster]

I don't quite understand what you propose. Can you post a code snippet?

[jpanther]

Does this need to reference .Page anyway? Given these are site config variables, can't we just access the global .Site directly?

[wolfspyre]

Does this need to reference .Page anyway? Given these are site config variables, can't we just access the global .Site directly?

wouldn’t using .Page enable one to disable lazy (or configure other attrs) at a per-page level?

if the only knobs this looks at are site-scoped doesn’t one lose this?

When asking on the hugo forums on how to enable a clean lookup hierarchy for partial config variables in site config[^] , I was steered towards Page scoped variables and using cascade…

not sure if that’s helpful or not… but it steers my thinking towards setting things to look for page-scoped knobs and set the page vars’ default to site …

[jpanther]

Well potentially, but why would you need to adjust the lazy loading preference on a per-page basis? That seems like something that you'd only control at a site level.