-
Notifications
You must be signed in to change notification settings - Fork 956
Open
Description
I've just noticed that our static-assets check doesn't catch everything we'd hope it does.
When we have images included via a Jinja macro (which is pretty common), I'm not sure those are being picked up by the scan that outputs the manifest, and which then drives the files we're looking for
For example, in this (now fixed) jinja macro call, we've got a reference to a .jpg as the default image, but that file doesn't exist in the codebase - only the .png version.
It's clear that the files ARE being collected, else they would error in prod, but it would be good to get them included in the manifest
Metadata
Metadata
Assignees
Labels
No labels