Upload saved cypher from another instance
I am able to connect a teammate to my populated instance on AuraDB using the username and password for the instance, but the 'saved cypher' doesn't get copied over and it would defeat the purpose of connecting to my instances if I have to manually add the saved queries. So far I can't find a way to import them. Is this possible? Thank you!
Node size based on relationships displayed
I know nodes can be dynamically sized based upon their properties. But it would be helpful if you had an option to dynamically size them within a perspective based on the incoming/outgoing relationships displayed
Increase size options 1-4 is too limited
I'm finding the size options for rule based sizing of relationships and nodes too limiting. E.g. imagine you are working with shareholder ownership based on a %. The size (thickness) of arrows for relationships is hardly noticeable between 1x and 4x. I also find the sizing of nodes too limiting e.g. the node is big or it's small, there's not enough variation. Could you please allow 1x to 10x sizing? This would help for rule based properties, and then also increase the maximum thickness of the relationship arrow / and node size. Thanks - It's getting v good.
Text wrapping in info doesn't break on words
The text/word wrapping in the info pane does not follow normal conventions making reading difficult.
bloom not support array
in bloom, i can't edit or filter nodes for properties which datatype is array.
TypeError: Failed to construct 'Worker'
Since latest Bloom update I am now getting the below error: TypeError: Failed to construct 'Worker': Module scripts are not supported on DedicatedWorker yet. You can try the feature with '--enable-experimental-web-platform-features' flag (see https://crbug.com/680046 ) I have set --enable-experimental-web-platform-features flags to "enabled" in both chrome and edge but still showing the error and won't render andy nodes/relationships
Create Relationship with NOT NULL Constraint
I'm sure this is related to the inability to edit relationship properties on the backend - a side effect is that if a relationship property is constrained to be NOT NULL, the inability to edit it means it cannot be initialized, meaning relationships with these constraints cannot be created through the interface at all. Would be very nice, given visual creation of relationships on the fly is a great use case for Bloom.