blog.axlight.com/posts/four-different-approaches-to-non-redux-global-state-libraries

Preview meta tags from the blog.axlight.com website.

Linked Hostnames

8

Thumbnail

Search Engine Appearance

Google

https://blog.axlight.com/posts/four-different-approaches-to-non-redux-global-state-libraries

Four different approaches to non-Redux global state libraries

Introduction Since React hooks landed, there has been many libraries proposed for global state. Some of them are simple wrappers around context. Whereas, some of them are full featured state management systems. Technically, there are several implementations how to store state and notify changes. We don’t go in detail in this post, but just note two axes. whether context based or external store whether subscriptions based or context propagation In this post, we focus on API design of hooks at the consumer end. In my observation, there are four approaches to the API design. Let’s see each approach by example in pseudo code. As a simple example, we assume an app that has the followings.



Bing

Four different approaches to non-Redux global state libraries

https://blog.axlight.com/posts/four-different-approaches-to-non-redux-global-state-libraries

Introduction Since React hooks landed, there has been many libraries proposed for global state. Some of them are simple wrappers around context. Whereas, some of them are full featured state management systems. Technically, there are several implementations how to store state and notify changes. We don’t go in detail in this post, but just note two axes. whether context based or external store whether subscriptions based or context propagation In this post, we focus on API design of hooks at the consumer end. In my observation, there are four approaches to the API design. Let’s see each approach by example in pseudo code. As a simple example, we assume an app that has the followings.



DuckDuckGo

https://blog.axlight.com/posts/four-different-approaches-to-non-redux-global-state-libraries

Four different approaches to non-Redux global state libraries

Introduction Since React hooks landed, there has been many libraries proposed for global state. Some of them are simple wrappers around context. Whereas, some of them are full featured state management systems. Technically, there are several implementations how to store state and notify changes. We don’t go in detail in this post, but just note two axes. whether context based or external store whether subscriptions based or context propagation In this post, we focus on API design of hooks at the consumer end. In my observation, there are four approaches to the API design. Let’s see each approach by example in pseudo code. As a simple example, we assume an app that has the followings.

  • General Meta Tags

    12
    • title
      Four different approaches to non-Redux global state libraries · Daishi Kato's blog
    • content-type
      text/html; charset=utf-8
    • viewport
      width=device-width, initial-scale=1.0, maximum-scale=1
    • description
    • article:section
      posts

  • Open Graph Meta Tags

    7
    • og:url
      https://blog.axlight.com/posts/four-different-approaches-to-non-redux-global-state-libraries/
    • og:site_name
      Daishi Kato's blog
    • og:title
      Four different approaches to non-Redux global state libraries
    • og:description
      Introduction Since React hooks landed, there has been many libraries proposed for global state. Some of them are simple wrappers around context. Whereas, some of them are full featured state management systems. Technically, there are several implementations how to store state and notify changes. We don’t go in detail in this post, but just note two axes. whether context based or external store whether subscriptions based or context propagation In this post, we focus on API design of hooks at the consumer end. In my observation, there are four approaches to the API design. Let’s see each approach by example in pseudo code. As a simple example, we assume an app that has the followings.
    • US country flagog:locale
      en_us

  • Twitter Meta Tags

    4
    • twitter:card
      summary_large_image
    • twitter:image
      https://blog.axlight.com/posts/four-different-approaches-to-non-redux-global-state-libraries/cover.jpg
    • twitter:title
      Four different approaches to non-Redux global state libraries
    • twitter:description
      Introduction Since React hooks landed, there has been many libraries proposed for global state. Some of them are simple wrappers around context. Whereas, some of them are full featured state management systems. Technically, there are several implementations how to store state and notify changes. We don’t go in detail in this post, but just note two axes. whether context based or external store whether subscriptions based or context propagation In this post, we focus on API design of hooks at the consumer end. In my observation, there are four approaches to the API design. Let’s see each approach by example in pseudo code. As a simple example, we assume an app that has the followings.

  • Link Tags

    3
    • stylesheet
      //cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css
    • stylesheet
      https://blog.axlight.com/css/style.css
    • stylesheet
      /css/custom.css

Links

18