@hulanbv/nest-utilities-client-state - npm Package Compare versions

Comparing version 0.0.4 to 0.0.5

package.json

		{
		"name": "@hulanbv/nest-utilities-client-state",
		"version": "0.0.4",
		"version": "0.0.5",
		"description": "React hooks for state management when using nest-utilities-client and a nest-utilities based API.",
		@@ -5,0 +5,0 @@ "main": "dist/index.js",

readme.md

		# nest-utilities-client-state

		<p align="center">
		An extension for <a href="https://github.com/MartinDrost/nest-utilities-client">nest-utilities-client</a>, providing an easy way to transition your HTTP services and data to a global state through React hooks.
		An extension for <a href="https://github.com/MartinDrost/nest-utilities-client">nest-utilities-client</a>, providing an easy way to transition your HTTP services and data to reusable state through React hooks.
		</p>
		@@ -16,3 +16,3 @@
		<p>
		Fetching data and updating user interfaces is a logic pattern we use all time time in our React apps. There are many ways of achieving a likewise pattern, think of simply fetching from `componentDidMount` or using a global state manager like Mobx or Redux. However you solve the problem, it will inevitably lead to a considerable amount of boilerplate code which has to be repeated every time data needs to be fetched -- let alone sharing data between multiple components.
		Fetching data and updating user interfaces is a logic pattern we use all the time in our React apps. There are many ways of achieving a likewise pattern, think of simply fetching from `componentDidMount` or using a global state manager like Mobx or Redux. However you solve the problem, it will inevitably lead to a considerable amount of boilerplate code which has to be repeated every time data needs to be fetched -- let alone sharing data between multiple components.
		</p>
		@@ -19,0 +19,0 @@ <p>

Worsened metrics