Processors¶
The processor takes the list of assets and renders the output to the page.
As assets are defined in the page, the AssetRegister will assign them to Processors, which it will in turn request to render them.
- class Processor¶
- aliases¶
A map (dict) of aliases to filenames.
This is useful for removing the need to, for instance, remember which version of jQuery your site is using.
- deps¶
A map of filenames or aliases to lists of other assets they depend on.
Any use of these assets will automatically add the listed dependencies.
- add_asset(filename, alias, deps)¶
Add an asset to this Processor. This is used by the {% asset %} tag.
- resolve_deps()¶
Return a list of filenames in an order which respects the declared dependencies. All aliasese will be resolved at this point.
- alias_map(name)¶
Unalias a given resource name.
Out of the box there are two processors: ScriptProcessor, and LinkProcessor.
ScriptProcessor¶
ScriptProcessor will output each asset in a script tag, after resolving the filename through staticfiles.
<script src="{% static filename %}"></script>
LinkProcessor¶
LinkProcessor will output each asset as a link tag. You can optionally specify in the config the rel and type attributes to be used.
<link rel="{{ rel }}" type="{{ type }}" href="{% static filename %}">