@graphty/graphty-element / session / ValidationResult
Interface: ValidationResult ​
Defined in: graphty-element/src/session/styles/Layer.ts:173
What checking a layer specification answered.
There is deliberately no match count here. Counting what a selector matches is a pass over the graph, which is the cost this whole design is arranged around; "how many would this match" is session.plan(), which is a command and says so.
Properties ​
errors ​
readonlyerrors: readonlyLayerProblem[]
Defined in: graphty-element/src/session/styles/Layer.ts:177
Everything wrong with it, all of it, so a form corrects a whole page in one round trip.
ok ​
readonlyok:boolean
Defined in: graphty-element/src/session/styles/Layer.ts:175
Whether the specification can be added as it stands.
shadowedPaths ​
readonlyshadowedPaths: readonlystring[]
Defined in: graphty-element/src/session/styles/Layer.ts:193
The bare graphty. paths read where the data also has a column of that name.
Not errors: every path starting graphty. reads a value graphty-element provides, never a column (graphty.notes.count is the note count). They are reported because the author may have meant the column, which reads as data.graphty.<name>.
unresolvedPaths ​
readonlyunresolvedPaths: readonlystring[]
Defined in: graphty-element/src/session/styles/Layer.ts:185
The paths that parsed but that nothing in this session answers.
Not errors: a selector naming a run that has not been started yet is a correct selector over a session that will answer it later. They are reported so that a consumer can say why a layer paints nothing instead of showing a confident empty screen.