fix(overmind): fix typing of operators

Author: christianalfoni

packages/node_modules/overmind/src/internalTypes.ts

@@ -166,23 +166,15 @@ type TActionValue<T> = T extends (a1: any, a2: infer TValue) => any
   ? TValue
   : never
 
-type TOperationValue<T> = T extends (
-  arg1: any,
-  arg2: infer IContext,
-  arg3: any
-) => any
-  ? (IContext extends { value: infer TValue } ? TValue : never)
-  : never
-
 export type ResolveActions<
   Actions extends NestedActions
 > = Actions extends undefined
   ? {}
   : {
       [T in keyof Actions]: Actions[T] extends IOperator<any, any, any>
-        ? TOperationValue<Actions[T]> extends void
+        ? TActionValue<Actions[T]> extends void
           ? () => Promise<void>
-          : (value: TOperationValue<Actions[T]>) => Promise<void>
+          : (value: TActionValue<Actions[T]>) => Promise<void>
         : Actions[T] extends IAction<any, any, any>
         ? TActionValue<Actions[T]> extends void
           ? () => ReturnType<Actions[T]>
@@ -209,9 +201,9 @@ export type ResolveMockActions<
   ? {}
   : {
       [T in keyof Actions]: Actions[T] extends IOperator<any, any, any>
-        ? TOperationValue<Actions[T]> extends void
+        ? TActionValue<Actions[T]> extends void
           ? () => Promise<MockResult>
-          : (value: TOperationValue<Actions[T]>) => Promise<MockResult>
+          : (value: TActionValue<Actions[T]>) => Promise<MockResult>
         : Actions[T] extends IAction<any, any, any>
         ? TActionValue<Actions[T]> extends void
           ? () => Promise<MockResult>

packages/overmind-website/guides/beginner/01_getstarted.md

@@ -19,13 +19,11 @@ h(Example, { name: "guide/getstarted/install" })
 h(TypescriptNotice, null, "Overmind requires Typescript version **3.2** or above")
 ```
 
-
-
 Great, we are good to go!
 
 ## Our first state
 
-Applications are about state and we are going to introduce our first state, **count**. Typically you would be tempted to isolate this state in your component, but this is exactly what Overmind discourages. In Overmind you primarily define the state of your application outside of your view layer. This gives you several benefits which will become clear as we move on.
+Applications are about state and we are going to introduce our first state, **count**. But we are not going to introduce this state through a component. We are going to take on the perspective of [UI as an implementation detail](). That means 
 
 Let us imagine we get what we need from Overmind in a component: