object-among-the-children

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 plain object is written among an element's children, where the runtime drops it and the page renders without it.

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

An object among children is not markup and the runtime has nothing to do with it, so it is replaced by a hole. Nothing throws and nothing is red — the page just renders without it, which is the slowest kind of wrong to find.

Almost always the line stopped a word early: {item} where {item.name} was meant. Where the whole object really is what you want to see, say how — {JSON.stringify(item)} in a debugging view, or a component that takes it as a prop and renders the parts.

An ARRAY is not this: the runtime flattens one into the children, so a group of nodes is markup and is never reported.

Next

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