state-management

We had two bug fixes in 1.4, both related to a change in admission control handler. We must write unit test to validate the expected behavior, so changes do not create a regression. Testing all the scenarios end-to-end is ideal, but we should at least have unit test for the handleRequest method in pkg/injector/injector.go.

It would be great to see, how to properly implement refreshing + pagination + search.

Describe the bug

dispatch.model.doAsync() √

dispatch({ type: 'mode/doAsync'}) X

Other information:

The documentation does not reflect strict mode. As an example in the Entity/Adapter documentation, the selectCurrentUser selector would give a null type error as userId is

Correct me if I'm wrong, but it seems to me that different effector-vue APIs (especially Options API vs. Hooks API) assume different Vue versions.

For example, I tried to use Hooks API in combination with Vue 2 & @vue/composition-api but it won't compile because it tries to import composition functions directly from vue module (as in Vue 3) instead of @vue/compositon-api module (as in V

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[x] Support request
[ ] Other... Please describe:

I'm writing a state that uses ngxsAfterBootstrap lifecycle event to initialise it.

I want to check in my test if the state is correctly initialised, but I can't find any doc on this ?

Could you please help me ?

Thanks.

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, 

Right now, the context updater function behaves almost like a reducer: it gives you the current context and you have to immutably return the next context.

It would be nice if it merging syntax like the old React's component-based setState.

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?

This needs to be done for:

• mobx
• flutter_mobx
• mobx_codegen