state-management

/area runtime

This feature applies only to the HTTP application protocol. This is not a usability issue with the gRPC API spec.

In some cases, the application may not need the full CloudEvent payload sent to the HTTP application. This is particularly the case with raw events, where receiving the CloudEvent wrapper is unexpected/confusing. This also avoids some performance hit in Base64 encod

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

Describe the bug

dispatch.model.doAsync() √

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

Copied from: nrwl/nx#1545

Please make sure you have read the submission guidelines before posting an issue

Expected Behavior

Please describe the behavior you are expecting

When running the below command without a --project flag, I expect the error message to reflect the missing fl

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 would like to use socket.io in my backend. Is there a way to connect to socket.io with websocket-plugin?

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?

The API docs for reactions do not show the various options available for autorun, reaction, when, asynWhen. This needs to be added.