Client State

State is typically managed on the client side.

Overview

Client state management refers specifically to the process of managing the state or data of a client-side application, such as a web or mobile application, in a way that allows it to be easily accessed, modified, and shared across different components of the application running on the client's device.

In this boilerplate we recommended for learn about this library.

There is a tree structure to handle state management across all running applications.

store
β”œβ”€β”€ i18n
β”‚   β”œβ”€β”€ <another reducer>
β”‚   └── index.ts //Combine reducers
β”œβ”€β”€ layout
β”‚   β”œβ”€β”€ <another reducer>
β”‚   β”œβ”€β”€ dashboardSlice.ts //Dashboard layout reducer
β”‚   └── index.ts //Combine reducers
β”œβ”€β”€ module
β”‚   β”œβ”€β”€ <another reducer>
β”‚   β”œβ”€β”€ userSlice.ts //User module reducer
β”‚   └── index.ts //Combine reducers
└── ui
    β”œβ”€β”€ <another reducer>
    β”œβ”€β”€ alertSlice.ts //UI alert reducer
    └── index.ts //Combine reducers

i18n

State i18n is used to handle all multilanguage state requirements. This is usually used for language switching in applications.

Layout

State layout is used to handle all state ui requirements related to system layout. Inside the boilerplate there are 3 main layouts, namely dashboard, landing, mobile. Sample code is in src/store/layout

Module

State modules are used to handle all the state module requirements of the application, for example the auth module, account, product etc.

UI

State ui is used to handle all state ui requirements related to the system user interface for example alerts, drawers etc.

Last updated