🐛bug: render issue of neo4j schema about g6vp

[nylqd]

Adjusting the ID retrieval sequence to include source and target node types sounds like a reasonable approach to address the issue stemming from the lack of sourceNodeType and targetNodeType in the Neo4j schema information during parsing.

An alternative solution is adding sourceNodeType and targetNodeType attributes during the parsing of Neo4j schema information seems like a promising approach to address the root cause of the rendering issue.

@pomelo-nwu I'd like some inputs from you to choose one solution over the other

[pomelo-nwu]

@nylqd t seems to be an issue with the EngineServer component:https://github.com/antvis/G6VP/blob/master/packages/gi-assets-neo4j/src/services/Engine.tsx#L1

[pomelo-nwu]

https://github.com/antvis/G6VP/blob/master/packages/gi-sdk/src/components/EngineServer/LoadGraph.tsx#L148
because I have switched to the pref/sdk-valtio branch for the upgrade of G6 5.0, which involves a lot of changes, I haven't switched to the master branch to investigate the issue for now. If possible, I would appreciate your help in resolving it.

[nylqd]

master/packages/gi-sdk/src/components/EngineServer/LoadGraph.tsx#L148 because I have switched to the pref/sdk-valtio branch for the upgrade of G6 5.0, which involves a lot of changes, I haven't switched to the master branch to investigate the issue for now. If possible, I would appreciate your help in resolving it.

@pomelo-nwu it seems indeed have bug in getSchemaGraph, i will do some digging around.

[pomelo-nwu]

@nylqd Considering that different graph database will use the same EngineServer component, I am more inclined towards the second solution.