value diagnostics · v1.14.0
A setting the grid cannot use is named, not ignored.
Hand the grid a value it does not understand and it used to fall back to a default without a word, so a mistyped option or a wrong type looked like a feature that never worked. Now the grid names the setting, says what it expected, and shows the value it saw, while it carries on rendering on the safe default. You find the mistake while you are building it, not weeks later when someone asks why a colour never took. A value the grid understands stays completely silent, so a warning always means a real setting to fix.
caught while you build
The wrong value tells you it is wrong.
A grid is a lot of settings, and one of them being off is easy to miss: a value pasted from another config, a mode named almost right, a number where the option wanted a word. The grid checks every value as it reads it and reports the ones it cannot use, each named with what it expected and what it received. The grid still renders, because the safe default is still there, but the value that would have quietly done nothing is now something you can see and fix in the same sitting. The check is deliberately careful: it never questions a value it understands, so a correct grid raises nothing and you never learn to ignore it.
what the grid is doing
The grid tells you what it is doing, as data.
When a grid feels slow or behaves in a way you did not expect, guessing is the slow way to the answer. The grid keeps a running account of its own work and hands it back to you: which settings you chose and which it chose for you, how the data is held, what each update cost, and everything it has flagged as probably a mistake. It is the same account the grid reads to decide what to skip, so the figures are what actually happened rather than an estimate taken from the outside. The demo above reads its own account, live, in your browser.
Nothing fails silently
A value the grid cannot use is named where you can see it, with what it expected and what it got. The grid still renders on the safe default, so you keep the mistake and lose nothing.
A correct grid stays quiet
The check never questions a value it understands, so a warning is always worth reading. You never learn to scroll past it, which is the only way a warning keeps its meaning.
A bundle you can just send
One call gathers settings, state, timings and warnings into a report you can send to support as is. It carries no row, cell or column values and says so, so nobody has to read it first.