decorator-that-adds-nothing

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 two decorators on one member give it the same thing — @persist beside @state, or one written twice.

The framework reports the same fault while running, as RMD050 — but only once the line actually runs. This is the same fault proved from the source instead.

One of the two lines does nothing, and that is the whole problem with it: it looks exactly like the line that does the work, so it survives every reading of the file and gets copied into the next component.

@state already puts a field in the hydration blob, so @persist beside it adds nothing — delete the @persist. Where the same decorator is written twice, delete one.

Two decorators doing DIFFERENT work on one member are not this: @created with @mounted, @onWindow with @onDocument, @watchProp with @updated each run twice on purpose, and neither this nor the framework says anything about them.

Next

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