fix(list): forward justify to filter controls

[markdumay]

Unblocked: gethinode/hinode#2115 shipped as hinode v3.18.0.

Problem

justify on the list block reached the section wrapper and the heading, but never the table.

utilities/section.html applies it as align-items-* to the column as a whole. With a width set, that centers the col-12 col-md-* wrapper and leaves its contents flush left, while assets/section-title.html separately centers the heading via mx-auto. On a filtered list the result is a centered heading above a left-aligned filter button group.

Change

Forward justify into $tableArgs so assets/table.html can position the filter row. The table itself is unaffected — it spans the full width of its container either way.

Merged in only when the author set it, rather than passed on every call:

{{ with .justify }}
    {{ $tableArgs = merge $tableArgs (dict "justify" .) }}
{{ end }}

Hinode is a separate module that a site resolves independently — it does not import mod-blocks — so the two versions can move apart. justify reached the table structure only in hinode v3.18.0, and an older copy rejects an unknown argument whatever its value. An unconditional forward therefore broke every list block for anyone updating mod-blocks alone:

ERROR partial [assets/table.html] - Invalid arguments: components/list.md
	[table] unsupported argument 'justify'

Guarding it narrows the requirement to the authors who actually set justify.

Verification

pnpm test passes.

• exampleSite/go.mod bumped to hinode v3.18.0
• Added a centered, filtered list fixture to exampleSite/content/components/list.md, which renders:

  class="table-filter-controls d-flex justify-content-center mb-3"
  

• Backward compatibility checked explicitly: rebuilt against hinode v3.16.3 with no justify set. Clean build. The unconditional version failed the same build on every list block, which is what motivated the guard.

Also verified end-to-end in a consuming site: the affected page renders the heading and the filter bar aligned.

Note

The earlier revision of this branch was committed with --no-verify, since its build could not pass before v3.18.0 existed. That is no longer the case — the hook passes on its own now.

🤖 Generated with Claude Code

[markdumay]

🎉 This PR is included in version 2.3.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀