Hello kind sir,

Problem

I am using your library when rendering CX networks. The node and edge properties can be read from the core without any problems. I am however having issues with cytoscape.js selectors, since the CX converter changes their property names (they append _u1, _u2 etc to distinguish properties I guess).

Steps to reproduce

The changes in network property names can be validated via this tool: https://frankkramer-lab.github.io/NDExEdit.

• Load this sample network via UUID: 5820d988-68d5-11e7-961c-0ac135e8bacf
• Select some nodes in the network
• Check the table of selected nodes for the property names

The respective section in the converter: https://github.com/cytoscape/cx2js/blob/master/src/cx_to_js.js#L418

Favored solution

As far as I know, the correct property names, that can be used to make selections on the core, are stored in the attributeNameMap, the CX converter uses during conversion. If you could extend the library to add another Output() containing this attributeNameMap, that would be awesome.

Project

• Angular 13.3.4
• Node: 16.15.0
• NgRx 13.1.0
• ngx-cytoscapejs 1.0.0

Problem

Loading network data from NDEx and storing the CX in my network.state.

As soon as the library is done with rendering, I store the received Cytoscapejs core in the network.state. Since I'm working immutable, I update my state as such:

  on(renderNetworkSuccess, (state: NetworkState, { core }): NetworkState => ({ ...state, core }))

The new reference re-triggers the rendering resulting in an endless loop that kills the app.

I tried moving the core into a separate state (graph.state), which would be fine for my use case, but it still triggers the update for all states (graph.state and network.state), which leads to the same problem. (See code from graph.state below)

  on(renderNetworkSuccess, (state: GraphState, {core}): GraphState => ({...state, core})),

Steps to reproduce

• Create a simple project with NgRx
• one state holding the network data
• store the resulting core in the same state
• watch your browser suffer

Favored solution

I would need persistent access to the core for further actions on the graph. Storing that in any of my states is mandatory for me. Maybe add an option to skip re-rendering the network with sort of a debounce time? Alternatively a separate input.

Project

• Angular 13.3.4
• Node: 16.15.0
• NgRx 13.1.0
• ngx-cytoscapejs 1.0.0

• https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics
• https://github.com/topics

Right now, toggeling the autoFit flag will resize and reposition the graph only on window resize. It would be brilliant, if on toggeling the autoFit (input changes to true), the graph would fit once, without the need for the window resize.

Hello :)

Problem

The CX2JS converter generates a backgroundColor, that could be applied to the canvas you're rendering the graph in (that's not a problem per se, but would be a nice feature).

You'll find the respective line of code here.

Steps to reproduce

A sample network that has a background color is 5820d988-68d5-11e7-961c-0ac135e8bacf (you can take a look at it here ). When using your library to render this network, the background stays white.

Favored solution

It would be great, if you could expand the @Inputs to allow users to toggle application of the background color.

Project

Angular 13.3.4 Node: 16.15.0 NgRx 13.1.0 ngx-cytoscapejs 1.0.0