User can link different nodes inputs with other nodes outputs

[scalamorphing]

No description provided.

[scalamorphing]

@nailxx I am going to rewrite horrible EditorBus service. It should be rewritten now using xstream. I need this event bus for managing every event we need to emit and broadcast in our components.

[nkrkv]

OK if it is required by the feature. It is.

[scalamorphing]

I deleted editor-remake branch and now I am working in feature-link-pins branch.

[scalamorphing]

Issue solution roadmap

1. Refactor EditorBus service using xstream.
2. Refactor all services of the application.
3. Write behaviour tests for this user story.

[scalamorphing]

I had a discussion with @brusherru and we found that derivablejs fits our needs entirely.

[scalamorphing]

Proposal

@nailxx @brusherru I am going to use ramda (since it's mature, it's recommended by author of derivablejs and it fits all our needs and even more) instead of immutable.js for managing state of client application. I am sure that side-effects should be localized for better testing experience. We should not fail into endless debugging of our tests. All components should be stateless. I guess that it's a good practice. If you are not sure if it's a good idea then I can spend some time on research.
At this moment I need stateless events: I must be sure that events data can't be changed because it would be really tedious to find such bugs while our appilcation growth.

[nkrkv]

No longer relevant