chore(*): move ng2-tree to Angular v5

Author: rychkog

.gitignore

@@ -13,3 +13,4 @@ node_modules
 *.swp
 npm-debug.log
 yarn-error.log
+package-lock.json

.npmrc

@@ -0,0 +1 @@
+package-lock=false

README.md

@@ -12,6 +12,7 @@
   - [tree](#tree)
   - [[tree]](#tree)
     - [Load children asynchronously](#load-children-asynchronously)
+    - [Load children using ngrx (or any redux-like library)](#load-children-using-ngrx-or-any-redux-like-library)
     - [Configure node via TreeModelSettings](#configure-node-via-treemodelsettings)
   - [[settings]](#settings)
   - [`Tree` class](#tree-class)
@@ -23,18 +24,20 @@
     - [NodeRenamedEvent](#noderenamedevent)
     - [NodeExpandedEvent](#nodeexpandedevent)
     - [NodeCollapsedEvent](#nodecollapsedevent)
+    - [LoadNextLevelEvent](#loadnextlevelevent)
 - [:gun: Controller](#gun-controller)
-    - [select - selecting a node](#select---selecting-a-node)
+    - [select - selects a node](#select---selects-a-node)
     - [isSelected - checks whether a node is selected](#isselected---checks-whether-a-node-is-selected)
     - [collapse - collapses a node](#collapse---collapses-a-node)
     - [isCollapsed - check whether a node is collapsed](#iscollapsed---check-whether-a-node-is-collapsed)
     - [expand - expands a node](#expand---expands-a-node)
-    - [isExpanded - checks wheather a node is expanded](#isexpanded---checks-wheather-a-node-is-expanded)
+    - [isExpanded - checks whether a node is expanded](#isexpanded---checks-whether-a-node-is-expanded)
     - [rename - renames a node (changes its value underneath)](#rename---renames-a-node-changes-its-value-underneath)
+    - [startRenaming - changes the node template so that text input appears and lets a user type a new name](#startrenaming---changes-the-node-template-so-that-text-input-appears-and-lets-a-user-type-a-new-name)
     - [remove - removes a node from the tree](#remove---removes-a-node-from-the-tree)
     - [addChild - creates a new child node](#addchild---creates-a-new-child-node)
   - [changeNodeId - changes node's id](#changenodeid---changes-nodes-id)
-  - [reloadChildren - load async children once more](#reloadchildren---load-async-children-once-more)
+  - [reloadChildren - loads async children once more](#reloadchildren---loads-async-children-once-more)
   - [setChildren - changes children of a node;](#setchildren---changes-children-of-a-node)
 - [SystemJS](#systemjs)
 - [Changes that should be taken into account in order to migrate from __ng2-tree V1__ to __ng2-tree V2__](#changes-that-should-be-taken-into-account-in-order-to-migrate-from-__ng2-tree-v1__-to-__ng2-tree-v2__)
@@ -154,7 +157,8 @@ Here is the fully stuffed *tree* tag that you can use in your templates:
       (nodeMoved)="handleMoved($event)"
       (nodeCreated)="handleCreated($event)"
       (nodeExpanded)="handleExpanded($event)"
-      (nodeCollapsed)="handleCollapsed($event)">
+      (nodeCollapsed)="handleCollapsed($event)"
+      (loadNextLevel)="handleNextLevel($event)">
     </tree>
 ```
 
@@ -286,6 +290,27 @@ Another worth noting thing is `loadChildren`. This function on `TreeModel` allow
 Node that defines this function is collapsed by default. At the moment of clicking 'Expand' arrow, it starts loading its children by calling given function.
 If `loadChildren` function is given to the node - `children` property is ignored. For more details - have a look at the [Demo](#eyes-demo).
 
+#### Load children using ngrx (or any redux-like library)
+
+You can also load children by changing the tree state using ngrx.
+The tree can emit an appropriate event notifying you to dispatch a new action in order to load the branch's children.
+
+To enable this feature you should set the ```TreeModel.emitLoadNextLevel``` property to true:
+
+ ```typscript
+ const model: TreeModel = {
+ emitLoadNextLevel : true
+ }
+ ```
+
+Now on the first time the node is expanded a __LoadNextLevelEvent__ will be fired (via the __loadNextLevel__ EventEmitter in the tree) containing the node that requested a next level (its children) loading.
+
+In your code make sure you change the tree state and add the children to the model.
+
+In addition the regular __NodeExpanded__ event will be fired.
+
+__NOTICE__: if both ```emitLoadNextLevel``` and ```loadChildren``` are provided, the tree will ignore the ```emitLoadNextLevel``` and the ```LoadNextLevelEvent``` won't be fired.
+
 #### Configure node via TreeModelSettings
 
 Apart from that `TreeModel` interface has an optional field called `settings` of type `TreeModelSettings`.
@@ -352,10 +377,6 @@ Also in the next section, you'll be reading about events generated by the `ng2-t
 
 ### events (nodeMoved, nodeSelected, nodeRenamed, nodeRemoved, nodeCreated, nodeExpanded, nodeCollapsed)
 
-Here is the diagram that shows tree events' hierarchy
-
-![tree events hierarchy](media/tree-events-hierarchy.png)
-
 `NodeEvent` is the root of the tree events' hierarchy. It defines property `node` that contains a receiver of the event action (`node` is an instance of the `Tree` class).
 
 `NodeDestructiveEvent` is the parent for all events that cause changes to the structure of the tree or to the node's value.
@@ -490,6 +511,24 @@ You can subscribe to `NodeCollapsedEvent` by attaching listener to `(nodeCollaps
 {node: <Tree>{...}}
 ```
 
+#### LoadNextLevelEvent
+
+You can subscribe to `LoadNextLevelEvent` by attaching a listener to `(loadNextLevel)` attribute.
+Relevant for loading children via ngrx (or any redux-inspired library).
+
+```html
+    <tree
+      [tree]="tree"
+      (loadNextLevel)="handleNextLevel($event)">
+    </tree>
+```
+
+`LoadNextLevelEvent` has a `node` property of the type `Tree`, which contains a node for which next level (its children) should be loaded.
+
+```typescript
+{node: <Tree>{...}}
+```
+
 ## :gun: Controller
 First of all you should know how to get a controller of a particular node. You can get a controller of a node only if you set an id property of a node. For example, your tree structure should look like:
 
@@ -625,6 +664,14 @@ oopNodeController.rename('new value');
 
 This method accepts a string and sets it as a node's new value, this action also fires rename event.
 
+#### startRenaming - changes the node template so that text input appears and lets a user type a new name
+
+```typescript
+oopNodeController.startRenaming();
+```
+
+After the user entered the new name a rename event will be fired.
+
 #### remove - removes a node from the tree
 
 ```typescript