Hi, I'm finding difficulty to manage custom number of connectors to the nodes. Right now, Diagram-Maker Nodes only support (one input and one output).

Also, please let us know, if it is possible to create custom-standard nodes in diagram maker.

Describe the issue with documentation I'm tryng to dynamically update the consumerData on a particular node, after it was created. What is the preffered way to update the store data? It would be nice to include this in the documentation or in the examples.

Is your feature request related to a problem? Please describe. In my action interceptors, for mouse / keyboard type of events, I'd like to receive the information about the original event that triggered the action - ex. left click or mouse wheel. This would allow me to get more information about the event, based on which I could make a decision - ex. if Ctrl key was held while selecting a node, add to the selection, instead of selecting only this node.

Describe the solution you'd like For events that originated from mouse / keyboard input type of events, automatically pass the original event data in the payload of the action, similar to how it is done in the event listeners.

Describe alternatives you've considered I considered stopping the native action in an action interceptor, and then using an event listener for input events, and passing my custom events with the original event data along side, but that is too messy and requires to overwrite a lot of the native action events.

This is an awesome project. I'm struggling with migrating a simple example to a Vuejs application.

I would really appreciate an example Vue.js. Is this something you're considering to include?

It would really help with the adoption of the library.

Many thanks

Is your feature request related to a problem? Please describe. I'd like to have scrollbars that I can use. It would help me with visual orientation on the workspace. I'd like to be able to scroll with the mouse wheel, instead of zooming in / out.

Describe the solution you'd like A configuration option to enable scrollbars. A configuration option to set the behaviour of the mouse wheel.

Describe alternatives you've considered I tried setting the css "overflow: scroll" on the "dm-view" element, so that I get the scrollbars. I tried intercepting the WORKSPACE_ZOOM action, stopping it, and instead dispatching a custom action to scroll. This custom action is updating the scrollTop property of the "dm-view" element, in order to scroll up and down. This works, but does not feel very natural. Also, I need to handle panning in a similar way. I think there should be a way to natively see and use scrollbars and to be able to configure the mouse wheel action.

To contextualize the nodes, it would be great if the nodes can be grouped. Similar to how the Cloud Formation Designer works where you can have a VPC and EC2 instances within it.

Could'nt find the documentation for setting up local run time environment for the package. Even though examples are given under integ directory, it uses compiled code to run. Adding details on how to locally run the source code would allow to run the package locally.

I'm trying to replace the background diagram-maker canvas svg, with custom small circular nodes. So, probably this lead to more than 5000 number of circular nodes.

This is causing Performance Issues. Any suggestions, how to optimize this usecase?

Hello,

When I make a diagram, I would like to be able to auto align every nodes. A misalignment in a diagram is not very important but people that see my diagram often make comments about it.

Describe the solution you'd like When you move a node, it snap to an imaginary/invisible strait line going through the middle of the closest node. The line could also be visible.

Best regards

Hello,

I often find myself making similar diagrams (or at least having some patterns coming back quite frequently). Instinctively I want to copy/paste my work.

Describe the solution you'd like I think the best or more intuitive solution would be :

1. Select mutliple nodes and edges
2. Hit ctrl + c
3. Hit ctrl + v
4. The selected nodes and edges are added to your canvas/workspace while keeping their states/connections/relative positions to each others

Best regards

Hello,

The library allows to select multiple nodes at the same time. It would be great if you could also move them all together.

Describe the solution you'd like Use the selection marquee tool to select multiple nodes. Click and drag one of them. The others follow while keeping their relative position to each others.

Describe alternatives you've considered Should it be a plugin or a core feature ?

Best regards

Is your feature request related to a problem? Please describe. The dagre package has been deprecated and diagram-maker has it as a dependency.

Describe the solution you'd like Remove dagre as a dependency and update the documentation

Bumps decode-uri-component from 0.2.0 to 0.2.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps deep-object-diff from 1.1.7 to 1.1.9.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps loader-utils from 1.4.0 to 1.4.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

This is an initial PR to get some eyes on the overall approach. Additional unit tests and integ tests are in progress, but I wanted to initiate the initial review on the high level changes.

Issue #, if available: https://github.com/awslabs/diagram-maker/issues/67

Description of changes:

• Add capability for edges to connect to individual custom connectors
• Allow consumer to configure the position of custom connectors

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I have an DiagramMaker running in VueJs component and I'm trying to destroy it in one of the lifecycle hooks. While the call to destroy happens I get this error. It happens every time the destroy is called.

beforeDestroy () { this.diagram.destroy() }