[viktorianer]

Since #2824, Linter#lint computes each rule's parser options before it merges this.config.framework into the lint context. When the framework comes only from the config, as with framework: actionview in .herb.yml and herb-lint on the command line, parserOptionsFor receives undefined. It falls back to DEFAULT_FRAMEWORK ("ruby") and turns action_view_helpers off for every rule that asks for it.

One visible effect: the body of a javascript_tag block is parsed as text instead of a <script> element, so html-no-unescaped-entities reports the JavaScript inside it.

<%= javascript_tag do %>
  if (a && b) {}
<% end %>

With framework: actionview in .herb.yml, herb-lint 0.11.0 reports nothing on this file. 0.11.1 reports two html-no-unescaped-entities warnings, and its unsafe autofix would turn the && into &&. Passing { framework: "actionview" } in the lint context still gives no offense, which is why the existing tests did not notice.

parserOptionsFor now gets the framework the way the lint context does: from the context, else from the config.

The new test lints that snippet once with the framework in the context and once with it only in the config, and expects no offense from either. It fails on main on the config path, with 2 offenses. The full linter suite passes with the change (250 files). A herb-lint built from this branch reports nothing on the snippet, and still reports a form_with nested inside another form_with.

🤖 Generated with Claude Code