Skip to content
#

context-api

Here are 930 public repositories matching this topic...

rluiten
rluiten commented Jul 31, 2020

I was just trying out react-sweet-state as it looks interesting and created a small to do list app to play with it.

I put an array of Todo objects in an array as the state of the store.
This produces no errors from typescript and even runs without error until you setState new values of the state.

The state of the store being an array is not supported as I later discovered in the react-sweet

johnmeunier
johnmeunier commented May 12, 2020

Some useful stuffs are missing (or is not explicit) from the documentation :

  • For test with identityserver, there is some better configuration :
    • response_type: 'code',
    • client_id: 'interactive.public',
  • For Chrome with blocked third parties cookie, you have to add the authority in authorized cookies to prevent "Authentification en cours" stuck
  • The "How to consume part" is n
SoaresMG
SoaresMG commented Jul 29, 2020

Issue Report

Right now the first time ResponsiveProvider runs it will use the first option on breakpoints (which normally is the smallest one).

Expected Behavior

It should render the correct breakpoint of first usage.

Actual Behavior

There is a jump from the initial breakpoint to the correct one after useEffect runs the first time.

Steps to Reproduce the Issue

Improve this page

Add a description, image, and links to the context-api 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 context-api topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.