class-instead-of-classname

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 an element carries class where Ramonda reads className.

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

Rename it to className. This is the one place the JSX deliberately differs from HTML, and it has to: class is a reserved word in the object literal a JSX factory receives.

The rename happens for you, so most of these are styled correctly and the page is fine. Two are not. An element carrying className as well keeps that one and drops this class silently. And a COMPONENT is renamed just the same — <Panel class=…> arrives as className, so a class prop that component declared reads undefined on every render.

A warning rather than an error, and it stays one: the common case renders exactly what was meant, and only the source is misleading.

Next

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