Sheath rule
statamic-required-tag-parameter
#Why
Several Statamic tags cannot determine their input from context. A missing or statically unusable parameter can produce an empty result or runtime failure.
#Examples
#Bad
{{-- collection needs a source, but none is provided. --}}
<s:collection />
#Good
{{-- Both forms identify the collection source. --}}
<s:collection from="articles" />
<s:collection:articles />
#Coverage
Built-in coverage follows Statamic 6 requirements for collections, taxonomies, partials, assets, forms, dictionaries, routes, Vite assets, authentication helpers, and other core tags.
Aliases and method suffixes are considered. Repeated static parameters follow Statamic's final-write behavior.
#Notes
Dynamic values and opaque attribute maps are skipped when they may provide the required input at runtime. Conditional attribute paths report when a reachable path is definitely missing the input.
Add-on tags and application replacements for core handles are outside the built-in requirements.
#See Also
Equivalent rules cover the other literal invocation forms:
- statamic-fluent-required-parameters: Check executed fluent calls
- statamic-tags-directive-required-parameters: Check
@tagsdefinitions - statamic-resource-exists: Verify literal project resources after input is present