The Wayback Machine - https://web.archive.org/web/20210516105615/https://github.com/topics/state-management
Skip to content
#

state-management

Here are 1,715 public repositories matching this topic...

keithpickering
keithpickering commented Mar 5, 2021

I love the way the @rematch/loading plugin keeps my app's loading state all in one place. Something that stuck out to me as odd was that there's no similar plugin for handling error/success state. So I can now avoid writing a { loading, error, success } object for every reducer, but error and success are still required if I want to perform some action after the effect finishes, so the ret

bloc
vinayluzrao
vinayluzrao commented Feb 26, 2021

Is your feature request related to a problem? Please describe.
Navigator 2.0 and Router have been released and are now the recommended approach:

Currently, there is no recipe for this, there are only recipes for a Navigator-less approach and for the old 1.0 imperative approach:

https://bloclibrary.dev/#/recipesflutternavigation

Describe the solution you'd like
Document a recipe

platform
Kamshak
Kamshak commented Jan 20, 2021

When using the *ngrxLet structural directive in an app, the view is cleared as soon as ngOnDestroy() is called. This causes an issue with animations: the view that is animated out changes as all ngrxLet templates get cleared.

To illustrate the problem see this StackBlitz, compare the ngIf behavior with ngrxLet: https://stackblitz.com/edit/ngrx-bug-ngrxlet

I believe the problem could be fixed

developer239
developer239 commented Jan 8, 2021

When I use removeItem state operator then TypeScript complains that message object can be possibly undefined even though I specified the type for removeItem operator. I could fix the issue with optional chaining but that is not possible if I want to use a utility library like Ramda

![image](https://user-images.githubusercontent.com/14946081/104027016-135aed80-51c7-11eb-9316-9b3dbf5b79bf

rgazelot
rgazelot commented Jan 6, 2021

Hello, I'm trying to type my application which is using redux-orm. I came across an issue with the new createSelector API. My code is as simple as:

import { createSelector } from 'redux-orm'
import orm from 'features/regulation/orm'

export const selectTest = createSelector(orm.Policy)

The error I get is that

Expected 2-9 arguments, but got 1.ts(2554)
redux.d.ts(87, 
drewg233
drewg233 commented Apr 25, 2018

I have a very big app and do not want to make a placeholder for each screen I would like to provide context to about what is loading. (And also do not want a general 'loading' message). Is there currently a way to change the title/subtitle easily for each ViewController, from the ViewController itself?

Improve this page

Add a description, image, and links to the state-management topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the state-management topic, visit your repo's landing page and select "manage topics."

Learn more