|
|
@@ -5,7 +5,7 @@ title: "Custom Stores"
|
|
|
permalink: docs/stores/
|
|
|
---
|
|
|
|
|
|
-> This section is about storing internal application state, if you work with React/Redux, for example. If none of this rings a bell, you can safely skip this section.
|
|
|
+> This section concerns storing the internal application state, if you work with React/Redux, for example. If none of this rings a bell, you can safely skip this section.
|
|
|
|
|
|
By default, Uppy stores its internal state in an object.
|
|
|
|
|
|
@@ -16,11 +16,11 @@ Uppy comes with two state management solutions (stores):
|
|
|
- `DefaultStore`, a simple object-based store.
|
|
|
- `ReduxStore`, a store that uses a key in a Redux store.
|
|
|
|
|
|
-There are also some third party stores:
|
|
|
+There are also some third-party stores:
|
|
|
|
|
|
- [uppy-store-ngrx](https://github.com/rimlin/uppy-store-ngrx/), keeping Uppy state in a key in an [Ngrx](https://github.com/ngrx/platform) store for use with Angular.
|
|
|
|
|
|
-## Using Stores
|
|
|
+## Using stores
|
|
|
|
|
|
To use a store, pass an instance to the [`store` option](/docs/uppy#store-defaultstore) in the Uppy constructor:
|
|
|
|
AJvanLoon