Merge pull request #484 from basicdays/readme-monkey-update

Add message in readme about support status of monkeys beneath an array node.

.editorconfig

@@ -0,0 +1,12 @@
+# EditorConfig is awesome: http://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 2

.gitignore

@@ -4,3 +4,5 @@ TODO.md
 benchmark.js
 *.log
 dist
+.idea/
+*.iml

.npmignore

@@ -1,5 +1,6 @@
 node_modules
 .DS_Store
+.editorconfig
 .gitignore
 .npmignore
 .travis.yml
@@ -12,3 +13,5 @@ benchmark.js
 .babelrc
 TODO.md
 bower.json
+.idea/
+*.iml

README.md

@@ -728,6 +728,7 @@ tree.set(['data', 'fromJack'], monkey({
 * The dynamic nodes are lazy and won't actually be computed before you get them (plus they will only compute once before they need to change, so if you get the same dynamic node twice, the computation won't rerun).
 * There are cases where it is clearly overkill to rely on a dynamic node. For instance, if only a single component of your app needs to access a computed version of the central state, then compute this version into the rendering logic of said component for simplicity's sake (a React component's render function for instance). Dynamic nodes are somewhat part of an optimization scheme.
 * Know that the `tree/cursor.serialize` method exists would you need to retrieve data stripped of dynamic nodes from your tree.
+* For the time being, placing monkeys beneath array nodes is not allowed for performance reasons.
 
 #### Specialized getters