browser-url

This fails the run. Where it is wrong about your code, // ramonda-check-ignore <reason> on the line says so, and the reason is printed on every run.

Reported when a component reads window.location in a project whose router already holds the answer.

The two are the same fact from two sources, and only one of them is reactive: read from the router, a component re-renders when the route moves; read from window, it is a snapshot taken once and never corrected, so the page quietly goes out of date. The router also keeps a distinction the URL hands over as one string — #tab=film is route state, #a-section names an element — so a hash tag with no value is a section and one with a value is not.

Next

• All rules — the other checks this one runs beside.
• Checking your app — how to run it, and what it proves.