Skip to content

Static-assets check has a gap #16932

@stevejalim

Description

@stevejalim

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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions