Ramonda

duplicate-decorators

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 single-use decorator is written twice: @catchError, @ShouldUpdateOnPropsChange or @StableProps.

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

A SUBCLASS declaring its own is an override, not a duplicate — only declarations on one class body are counted here.

Next