Overview - Herb

herbWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

herb

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

Succeeded
analysis/constant-identity
9bebf389 Analysis: Never call a constant an identity once the map travels `for` said a constant was derived and `across` said it was an identity, and `across` is the one whose answer is delivered. A client reading that map is told it can write `<%= Post.count %>` by copying a value it has never been given. A partial's incoming locals are not among the names it declares, so the names carried by the trace are treated as settable to make a partial answer in its caller's terms. Constants arrive by the same door and are not settable by anything, which is what `for` had right and `across` lost. The map already left constants out of the request names, so nothing could reach one by the name a request uses. That is what kept this from being reachable in practice, and it is not the same as the map being right.
by Marco Roth

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools