Skip to content
#

state-management

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

platform
react-final-form
quicksnap
quicksnap commented Apr 9, 2020

Hey Erik! How's it been?

Are you submitting a bug report or a feature request?

Feature

What is the current behavior?

No mention of withTypes in the documentation.

What is the expected behavior?

༼ つ ◕_◕ ༽つ

I just found out about this from a co-worker and am not even sure yet what it exactly was! Excited to see..

splincode
splincode commented Oct 27, 2019

Description

I'm on 3.5.1 and it seems that things are still initialized before APP_INITIALIZER.
Not sure if I'm missing something or if I don't completely understand what this issue's resolution should be?

This is my use case:
I need to initialize Ngxs through a library module that either is imported or not in the apps (monorepo structure)
And I couldn’t find a way to initialize it pr

videni
videni commented Sep 29, 2019

what is prefer way to add relation and remove relation? I found example as below, but I did't find any document about the two methods.

 case 'ADD_AUTHOR_TO_BOOK':
        Book.withId(action.payload.bookId).authors.add(action.payload.author);  // add new entity ,  add relation?  this doesn't work.
        break;
    case 'REMOVE_AUTHOR_FROM_BOOK':
        Book.withId(action.payload.bo
final-form
ismay
ismay commented Jul 31, 2019

Are you submitting a bug report or a feature request?

Neither, reporting missing documentation

What is the current behavior?

Detailed documentation on the signature of mutator functions is missing.

What is the expected behavior?

I'd expect the docs on mutators to be more elaborate on both the definition and the usage of mutators. I've looked at the docs for react

AlexanderArendar
AlexanderArendar commented Dec 27, 2019

In the release notes for 4.0.0 I've found this useful piece:

The new create/update callbacks are lazy-loaded, which means they are called the first time the value is read instead of the first time the provider is created.

If this is undesired, you can disable lazy-loading by passing lazy: false to the provider of your choice:

FutureProvider(
  create: (_) async => doSomeHttpReques
PierreCapo
PierreCapo commented Apr 8, 2020

The documentation explains pretty well why:

Wrap ALL of your components with view - including class and function ones - even if they don't seem to directly use a store.

I think it's pretty easy to miss adding this view hoc when you write hundred of components. My question is: Is there an eslint rule which exists to warn you that you forgot to add this extra view?

It could be nice to

Guria
Guria commented Mar 2, 2017

Please leave info about your projects using Cerebral and function tree.
I am prepaing internal presentation on corporate event and I need some cool reference to mention in it. And of course we can include references to your projects on docs website if you want.

Please provide:

  • short description
  • a link to project if available
  • screenshots and/or dynamic gif (especially @gaspard app with
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?

CharlesStover
CharlesStover commented Sep 1, 2019

This Issue serves as documentation for anticipated breaking changes in 3.0 and allows community feedback to drive the development process.

Breaking Changes 💔

  • Do not re-export React from reactn. Have users just import React and ReactN Component/hooks from separate packages. This will help with the namespace conflicts with Component in TypeScript.
  • Remove support for @reactn decora
aweary
aweary commented May 5, 2017

The idea of deferring state management to freactal is solid but as far as I can tell, users will still need to use class components if they want to trigger effects in lifecycle methods, and the README seems to imply that you can always use SFCs because freactal is orchestrating state, but that feels slightly misleading since React provides more than just state management APIs

Maybe add an e

vuex-pathify

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

You can’t perform that action at this time.