compute-takes-no-arguments

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 @compute declares a parameter, and its cache is keyed by nothing so the argument is ignored.

A @compute has no key: one value per component, recomputed when something it READ changes. So an argument has nowhere to go — it is accepted and ignored.

When the value differs per argument, @memoized is the decorator keyed by them:

@memoized rowConfig(id: string) { return { id, href: `/rows/${id}` } }

One cached value per argument, per instance, dropped when a render stops asking for it. See /concepts/caching for the whole comparison.

The framework refuses this too, when the class definition runs — which is when the module is first imported. A component behind a route nobody opened would ship with it and throw for whoever opens that route, which is why it is reported here as well.

Next

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