Typescript

Overmind is written in Typescript and it is written with a focus on you dedicating as little time as possible to help Typescript understand what your app is all about. Typescript will spend a lot more time helping you. If you are not a Typescript developer Overmind is a really great project to start learning it as you will get the most out of the little typing you have to do.
Configuration
First we need to define the typing of our configuration and there are two approaches to that.
1. Declare module
The most straightforward way to type your application is to use the declare module approach. This will work for most applications, but might make you feel uncomfortable as a hardcore Typescripter. The reason is that we are overriding an internal type, meaning that you can only have one instance of Overmind running inside your application.
overmind/index.ts
overmind/index.ts
import { IConfig } from 'overmind'
​
const config = {}
​
declare module 'overmind' {
  // eslint-disable-next-line @typescript-eslint/no-empty-interface
  interface Config extends IConfig<{
    state: typeof config.state,
    actions: typeof config.actions,
    effects: typeof config.effects
  }> {}
  // Due to circular typing we have to define an
  // explicit typing of state, actions and effects since
  // TS 3.9
}
Now you can import any type directly from Overmind and it will understand the configuration of your application. Even the operators are typed.
import {
  Context,
  RootState,
  pipe,
  map,
  filter,
  ...
  // These are primitive types in Overmind you typically
  // do not need
  Action,
  AsyncAction,
  Operator
} from 'overmind'
2. Explicit typing
You can also explicitly type your application. This gives more flexibility.
overmind/index.ts
overmind/index.ts
import {
  IConfig,
  IOnInitialize,
  IContext,
} from 'overmind'
​
export const config = {}
​
// Due to circular typing we have to define an
// explicit typing of state, actions and effects since
// TS 3.9
export interface Config extends IConfig<{
  state: typeof config.state,
  actions: typeof config.actions,
  effects: typeof config.effects
}> {}
​
export interface OnInitialize extends IOnInitialize<Config> {}
​
export interface Context extends IContext<Config> {}
​
export type RootState = Context['state']
​
/*
  NOTE! These types are typically not needed, but represents
  primitives in Overmind which you might want to pass as
  arguments etc.
*/
export interface Action<Input = void, Output = void> extends IAction<Config, Input, Output> {}
​
export interface AsyncAction<Input = void, Output = void> extends IAction<Config, Input, Promise<Output>> {}
​
export interface Operator<Input = void, Output = Input> extends IOperator<Config, Input, Output> {}
​
export interface Operator<Input = void, Output = Input> extends IOperator<Config, Input, Output> {}
​
You only have to set up these types once, where you bring your configuration together. That means if you use multiple namespaced configuration you still only create one set of types, as shown above.
Now you only have to make sure that you import your types from this file, instead of directly from the Overmind package.
The Overmind documentation is written for implicit typing. That means whenever you see a type import directly from the Overmind package, you should rather import from your own defined types.
State
The state you define in Overmind is just an object where you type that object.
overmind/state.ts
overmind/state.ts
type State = {
  foo: string
  bar: boolean
  baz: string[]
  user: User
}
​
export const state: State = {
  foo: 'bar',
  bar: true,
  baz: [],
  user: new User()
}
It is important that you use a type and not an interface. This has to do with the way Overmind resolves the state typing. 
When writing Typescript you should not use optional values for your state (?), or use undefined in a union type. In a serializable state store world null is the value indicating “there is no value”.
type State = {
  // Do not do this
  foo?: string
​
  // Do not do this
  foo: string | undefined
​
  // Do this
  foo: string | null
​
  // Or this, if there always will be a value there
  foo: string
}
​
export const state: State = {
  foo: null
}
Derived
overmind/state.ts
overmind/state.ts
import { derived } from 'overmind'
​
type State = {
  foo: string
  shoutedFoo: string
}
​
export const state: State = {
  foo: 'bar',
  shoutedFoo: derived((state: State) => state.foo + '!!!')
}
Note that the type argument you pass is the object the derived is attached to, so with nested derived:
overmind/state.ts
overmind/state.ts
import { derived } from 'overmind'
​
type State = {
  foo: string
  nested: {
    shoutedFoo: string
  }
}
​
export const state: State = {
  foo: 'bar',
  nested: {
    shoutedFoo: derived((state: State['nested']) => state.foo + '!!!')
  }
}
Note that with Explicit Typing you need to also pass the a third argument to the derived function, the Config type created in your main index.ts file.
overmind/state.ts
overmind/state.ts
import { RootState } from 'overmind'
​
type State = {
  foo: string
  shoutedFoo: string
}
​
export const state: State = {
  foo: 'bar',
  shoutedFoo: derived(
    (state: State, rootState: RootState) => state.foo + '!!!'
  )
}
Statemachine
Read the guide on Using state machines to understand how to type them.
Actions
You type your actions with the Context and an optional value. Any return type will be inferred.
import { Context } from 'overmind'
​
export const noArgAction = (context: Context) => {
  // actions.noArgAction()
}
​
export const argAction = (context: Context, value: string) => {
  // actions.argAction("foo"), requires "string"
}
​
export const noArgWithReturnTypeAction = (context: Context) => {
  // actions.noArgWithReturnTypeAction(), with return type "string"
  return 'foo'
}
​
export const argWithReturnTypeAction = (context: Context, value: string) => {
  // actions.argWithReturnTypeAction("foo"), requires "string" and returns "string"
  return value + '!!!'
}
Any of these actions could be defined as an async function or simply return a promise to be typed that way.
Effects
There are no Overmind specific types related to effects, you just type them in general.
overmind/effects.ts
overmind/effects.ts
export const api = {
  getUser: async (): Promise<User> => {
    const response = await fetch('/user')
    
    return response.json()
  }
}
Operators
Operators is like the action: it can take an optional value, but it always produces an output. By default the output of an operator is the same as the input.
overmind/operators.ts
overmind/operators.ts
import { Context, mutate, filter, map } from 'overmind'
​
// Use the Context type for the first argument
export const changeSomeState = mutate(({ state }: Context) =>  {
  state.foo = 'bar'
})
​
// Type the value as the second argument
export const filterAwesomeUser = filter((_: Context, user: User) => {
  return user.isAwesome
})
​
// The output is inferred
export const toNumber = map((_: Context, value: number) => { 
  return Number(value)
})
When you create a pipe that has an input when it is called you only need to type the first operator value.
import { Context, pipe, map, mutate } from 'overmind'
​
export const doThis = pipe(
  map((context: Context, value: string) => {
    // actions.doThis("foo"), requires "string"
    return 123
  }),
  mutate((context: Context, value) => {
    // value is now "number"
  })
Core - Previous
Server Side Rendering
Next - views
React
Last updated 2 months ago