Fix: Prevent Undefined nodes and edges in GraphCreator Initialization #183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR ensures that
nodes
andedges
properties inGraphCreator
are always initialized as arrays, preventing potentialundefined
errors when processing uploaded files.Changes
CypherController.js
:nodes
andedges
to default to empty arrays ([]
) ifreq.files.nodes
orreq.files.edges
areundefined
.Reason for Change
req.files.nodes
orreq.files.edges
is missing,GraphCreator
would receiveundefined
, potentially causing runtime errors during graph parsing.map()
andforEach()
, do not fail.Impact
GraphCreator
always has validnodes
andedges
arrays to work with.