refactor(dashboard): use React Hooks API for state management

...and move all data to a single data provider.
garden-io · Jan 25, 2019 · 588dd6c · 588dd6c
1 parent cdcdb64
commit 588dd6c
Show file tree

Hide file tree

Showing 17 changed files with 523 additions and 387 deletions.
diff --git a/dashboard/README.md b/dashboard/README.md
@@ -68,4 +68,6 @@ The app is structured into presentational components (`src/components`), contain
 
 **Provider/consumer components:** These are re-usable components that contain "global" data that needs to be accessible by many (presentational) components in the tree. The provider/consumer pattern is a part of the new [React context API](https://reactjs.org/docs/context.html).
 
-Maintaining this separation will make it easier to migrate to different state management patterns/tools as the app evolves.
+Maintaining this separation will make it easier to migrate to different state management patterns/tools as the app evolves.
+
+We also use the new [React Hooks API](https://reactjs.org/docs/hooks-intro.html) to manage data and state.