GitBook: [master] 2 pages modified

Author: christianalfoni

core/defining-state.md

@@ -113,10 +113,6 @@ export const state = {
 {% endtab %}
 {% endtabs %}
 
-{% hint style="warning" %}
-It is import that you do **NOT** use arrow functions on your methods. The reason is that this binds the context of the method to the instance itself, meaning that Overmind is unable to proxy access and allow you to do tracked mutations
-{% endhint %}
-
 You can now use this instance as normal and of course create new ones.
 
 {% hint style="info" %}

core/running-side-effects.md

@@ -132,6 +132,35 @@ export const onInitialize = async ({ effects }) => {
 Typically you explicitly communicate with effects from actions, by calling methods. But sometimes you need effects to know about the state of the application, or maybe some internal state in the effect should be exposed on your application state. Again we can take advantage of an **initialize** method on the effect:
 
 {% tabs %}
+{% tab title="overmind/effects.js" %}
+```javascript
+// We use an IIFE to isolate some variables
+export const socket = (() => {
+  _options
+  _ws
+  return {
+    initialize(options) {
+      _options = options
+      _ws = new WebSocket('ws://...')
+      _ws.onclose = () => options.onStatusChange('close')
+      _ws.onopen = () => options.onStatusChange('open')
+      _ws.addEventListener(
+        'message',
+        (event) => options.onMessage(event.data)
+      )
+    },
+    send(type, data) {
+      _ws.postMessage({
+        type,
+        data,
+        token: _options.getToken()
+      })
+    }
+  }
+})()
+```
+{% endtab %}
+
 {% tab title="overmind/onInitialize.js" %}
 ```typescript
 export const onInitialize = async ({ state, effects, actions }) => {