Linter Rule: Prefer partial paths qualified from the view root

Rule: actionview-prefer-qualified-partial-path

Description

Detects render calls that name a partial without a directory, such as render "card", where the file resolved depends on which template the call appears in.

Rationale

An unqualified name is resolved relative to the directory of the template doing the rendering, so the same call renders different files depending on where it lives:

<%# app/views/posts/index.html.erb %>
<%= render "card" %>
The partial `card` is looked up relative to the directory of the template rendering it. Moving this template changes which file that resolves to, and renaming the partial means hunting for callers that never spell its full name. Write the full path from the view root so it resolves to the same file from any template, and a search for that path finds every caller. (actionview-prefer-qualified-partial-path)

That reads app/views/posts/_card.html.erb, or app/views/application/_card.html.erb if the first does not exist. Neither is visible from the call.

Writing the path from the view root removes the dependency on context:

<%= render "posts/card" %>

Three things get easier. Searching for every caller of a partial finds them, because they all spell it the same way. Moving a template to another directory no longer silently changes which partial it renders. And renaming the partial becomes a matter of updating the callers that a search actually turns up.

Herb's partial index gains from it too. A qualified name resolves to the same entry from any template, so the language server can jump from the call to the partial and back to every caller, rename a strict local across all of those call sites at once, complete the locals a partial declares as you type them, and report a call that passes a local the partial does not declare or omits one it requires. An unqualified name has to be resolved from wherever the call happens to sit, and two calls that look like they render the same partial may not.

Short names are idiomatic Rails and extremely common, so this reports at info: it is guidance for codebases that want their template dependencies explicit and greppable, not a defect report.

When the project's partials are known, the message names the path to write. Otherwise it asks for the full path without guessing at one.

Only output tags are reported. A render in a silent <% %> tag discards its output and is covered by actionview-no-silent-render.

Examples

✅ Good

<%= render "posts/card" %>

<%= render partial: "posts/card", locals: { post: @post } %>

<%= render partial: "admin/posts/card", collection: @posts %>

🚫 Bad

<%= render "card" %>
The partial `card` is looked up relative to the directory of the template rendering it. Moving this template changes which file that resolves to, and renaming the partial means hunting for callers that never spell its full name. Write the full path from the view root so it resolves to the same file from any template, and a search for that path finds every caller. (actionview-prefer-qualified-partial-path)

<%= render partial: "card", locals: { post: @post } %>
The partial `card` is looked up relative to the directory of the template rendering it. Moving this template changes which file that resolves to, and renaming the partial means hunting for callers that never spell its full name. Write the full path from the view root so it resolves to the same file from any template, and a search for that path finds every caller. (actionview-prefer-qualified-partial-path)

Configuration

Disable it in .herb.yml when short partial names are the house style:

linter:
  rules:
    actionview-prefer-qualified-partial-path:
      enabled: false

References

• Action View - Rendering partials