Use a standard state management library [ngrx/store] and strategy

[harunurhan]

Overtime even this app is getting big and having more and more components. And naturally there are some state that are required by different components that are no where to close each other in the app hierarchy. Thus we'll have to use multiple @Input and @Output combinations to share a single state, which is ugly and not scalable at all.

Another thing we do sometimes (not always so no consistency here) to solve this problem, use different services with both observable and non reactive regular variables (no consistency again)

Which is why I think we should start using https://github.com/ngrx/platform which is like rxjs powered react for angular.

And if a state goes out of an component scope, it has to be part of more global scope. Although we can make some exceptions for 1 level nested @output and @input passing if it makes too much sense.

This is an issue not only concerning record-editor but also https://github.com/inveniosoftware-contrib/ng2-json-editor (even though some cases not fit for ngrx, so needs to be evaluated separately) and https://github.com/inspirehep/ng2-multi-record-editor (@Glignos)