GitBook: [master] 4 pages modified

Author: christianalfoni

core/defining-state.md

@@ -70,6 +70,13 @@ Are things loading or not, is the user logged in or not? These are typical uses
 
 All values, with the exception of booleans, can also be **null**. Non-existing. You can have a non-existing object, array, string or number. It means that if we haven’t selected a mode, both the string version and number version would have the value **null**.
 
+## Undefined
+
+You might wonder why **undefined** is not part of the core value types. Well, there are two reasons:
+
+1. It is not a serializable value. That means if you explicitly set a value to _undefined_ it will not show up in the devtools
+2. Undefined values can not be tracked. That means if you were to iterate an object and look at the keys of that object, any undefined values will not be tracked. This can cause unexpected behaviour
+
 ## Class values
 
 Overmind also supports using class instances as state values. Depending on your preference this can be a powerful tool to organize your logic. What classes provide is a way to co locate state and logic for changing and deriving that state. In functional programming the state and the logic is separated and it can be difficult to find a good way to organize the logic operating on that state.
@@ -389,13 +396,6 @@ You can reset the state of a statemachine, which also runs the exit of the curre
 state.mode.reset()
 ```
 
-## Undefined
-
-You might wonder why **undefined** is not part of the core value types. Well, there are two reasons:
-
-1. It is not a serializable value. That means if you explicitly set a value to _undefined_ it will not show up in the devtools
-2. Undefined values can not be tracked. That means if you were to iterate an object and look at the keys of that object, any undefined values will not be tracked. This can cause unexpected behaviour
-
 ## Deriving state
 
 ### Getter

core/typescript.md

@@ -387,43 +387,7 @@ export const filterAwesome: <T extends { isAwesome: boolean }>() => Operator<T>
 
 That means this operator can handle any type that matches an **isAwesome** property, though will pass the original type through.
 
-## Statemachine
-
-Statemachines exposes a type called **Statemachine**, though it is strictly not necessary to use as it is recommended to separate your machine definition from your state using the factory:
-
-{% tabs %}
-{% tab title="overmind/state.ts" %}
-```typescript
-import {statemachine } from 'overmind'
-
-type Modes =
-  | 'unauthenticated'
-  | 'authenticating'
-  | 'authenticated'
-  | 'unauthenticating'
-  
-const mode = statemachine<Modes>({
-  initial: 'unauthenticated',
-  states: {
-    unauthenticated: ['authenticating'],
-    authenticating: ['unauthenticated', 'authenticated'],
-    authenticated: ['unauthenticating'],
-    unauthenticating: ['unauthenticated', 'authenticated']
-  }
-})
-
-type State = {
-  mode: typeof mode
-}
-
-export const state: State = {
-  mode
-}
-```
-{% endtab %}
-{% endtabs %}
-
-## Statechart
+## Statecharts
 
 To type a statechart you use the **Statechart** type:
 

faq.md

@@ -8,9 +8,5 @@ First… try to refresh your app to reconnect. If this does not work make sure t
 
 Restart VS Code
 
-## My operator actions are not running?
-
-Operators are identified with a Symbol. If you happen to use Overmind across packages you might be running two versions of Overmind. The same goes for core package and view package installed out of version sync. Make sure you are only running on package of Overmind by looking into your **node\_modules** folder.
-
 
 

views/angular.md

@@ -39,7 +39,7 @@ import { AppComponent } from './app.component';
   declarations: [ AppComponent ],
   bootstrap: [ AppComponent ],
   providers: [
-    { provide: OVERMIND_INSTANCE, useFactory: () => createOvermind(config) },
+    { provide: OVERMIND_INSTANCE, useValue: createOvermind(config) },
     { provide: Store, useExisting: OvermindService }
 ]
 })
@@ -85,9 +85,7 @@ if (environment.production) {
 platformBrowserDynamic()
   .bootstrapModule(AppModule, {
     // We do not need zones, we rather use the tracking
-    // directive, which gives us a pretty signifcant performance
-    // boost. Note that 3rd party libraries might need ngZone,
-    // in which case you can not set it to "noop"
+    // directive, which gives us a huge optimization
     ngZone: "noop"
   })
   .catch(err => console.log(err));
@@ -126,7 +124,7 @@ You can now access the **admin** state and actions directly with **state** and *
 
 ## NgZone
 
-The Overmind **\*track** directive knows when your components should update, and so is much more efficient at change detection than Angular's default NgZone. In order to take advantage of the efficiency provided by the \***track** directive, you _must_ set **ngZone** to "noop". Note that other 3rd party libraries may not support this. If for any reason you can't set **ngZone** to "noop", then the \***track** directive is redundant, and you can safely exclude it from your templates.
+Since Overmind knows when your components should update you can safely turn **ngZone** to `"noop"`. Note that other 3rd party libraries may not support this.
 
 ## Rendering