Skip to content
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.

Fixes for 0.6.0 #106

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fixes for 0.6.0 #106

wants to merge 1 commit into from

Conversation

stellasia
Copy link
Owner

@stellasia stellasia commented Oct 31, 2021

Small fixes after manual tests:

  • Fix relationship type selection (r:RELATIONSHIP doesn't seem to be valid Cypher)
  • Make sure we show the layer name in the layer control and not the ukey which is meaningless for the user
    TODO: fix couple more issues (I, @nikita03565 , will handle this):
  • app crashes when there are no nodes found
  • app crashes when db with name saved in local storage no longer exists

Prepare for 0.6.0 release:

  • Version bump in packages.json
  • Update release notes

@@ -177,7 +177,7 @@ export class Layer extends Component {
if (relationshipLabel != null && relationshipLabel.length > 0) {
let sub_q = "(false";
relationshipLabel.forEach((value) => {
sub_q += ` OR r:\`${value.label}\``;
sub_q += ` OR type(r) = '${value.label}' `;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i tested it and it was working for me 🤔
maybe it depends on cypher/neo4j version, i'll double check this

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was surprised too because it seemed to me I had already tested it, but tested in a Cypher shell and raises the same error. Documentation here: https://neo4j.com/docs/cypher-manual/4.3/clauses/where/#filter-on-relationship-type, only mention the "type(r)" method, so I think it is safer to go this way.

@@ -210,7 +210,7 @@ export const Map = React.memo(({ layers, sideBarCollapsed }) => {
break;
}

layerControl.addOverlay(newMapOverlays[ukey], ukey);
layerControl.addOverlay(newMapOverlays[ukey], name);
Copy link
Collaborator

@nikita03565 nikita03565 Oct 31, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm still showing name to user 🤔 ah, i got what names you're talking about
changed this intentionally because having multiple layers with the same name (e.g. "New Layer") was leading to issues with layers deletion/updates. if i remember correctly the last created layer was getting deleted instead of the one i wanted to delete

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I see, I'll experiment layer deletion, I think we can remove a layer without using its name (?), otherwise I'll rollback this update.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants