Skip to content

{% cache %} should use CacheModel #3

@ironfroggy

Description

@ironfroggy

This would allow an exposure of the template cache blocks that one could introspect, update, and invalidate outside the normal render workflow. If a cache block can be identified by a path to the template, a path of the nested block names, and the final inherited set of keys, a CacheModel can be automatically created using all those as keys.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions