@graphty/graphty-element / index / DataLoadingCompleteEvent
Interface: DataLoadingCompleteEvent ​
Defined in: graphty-element/src/events.ts:316
Properties ​
duration ​
duration:
number
Defined in: graphty-element/src/events.ts:338
edgesLoaded ​
edgesLoaded:
number
Defined in: graphty-element/src/events.ts:337
How many edges the graph HOLDS after the load.
It used to count edge records handed over, which is a different number and was wrong by the whole file whenever the endpoint columns did not resolve: miserables.json reported 254 next to a graph holding zero. The record count is still published, under the name that says what it is, as report.counts.edgeRecords.
errors ​
errors:
number
Defined in: graphty-element/src/events.ts:339
format ​
format:
string
Defined in: graphty-element/src/events.ts:318
loadId? ​
optionalloadId?:number
Defined in: graphty-element/src/events.ts:349
Which load this is about: the id addDataFromSource, loadFromFile and loadFromUrl resolve to, and that every event about one load carries. Absent on a report about records handed to a setter, which is not a load.
nodesLoaded ​
nodesLoaded:
number
Defined in: graphty-element/src/events.ts:328
How many nodes the graph HOLDS after the load.
It used to count the node records the source handed over, which is a different number whenever an edge names a node the file never declares -- the graph creates that node, and the event then disagreed with session.status.counts.nodes about a graph neither of them was wrong about. Both numbers are still published: the record count is report.counts.nodeRecords.
report ​
report:
ImportReport
Defined in: graphty-element/src/events.ts:343
What the load did: the endpoint spelling, the repeat policy, and every count.
success ​
success:
boolean
Defined in: graphty-element/src/events.ts:341
type ​
type:
"data-loading-complete"
Defined in: graphty-element/src/events.ts:317
warnings ​
warnings:
number
Defined in: graphty-element/src/events.ts:340