subspace-docs/getting-started.md

159 lines
5.4 KiB
Markdown
Raw Normal View History

2019-09-03 14:40:19 -04:00
# Getting Started
## Installation
2019-09-27 15:24:05 -04:00
**Subspace** can be used in browser, node and native script environments. To get started install the package `@status-im/subspace` using `npm` or `yarn` by executing this command in your project directory:
2019-09-03 14:40:19 -04:00
```bash
# Using npm
2019-09-27 15:24:05 -04:00
npm install --save @status-im/subspace
2019-09-03 14:40:19 -04:00
# Using yarn
2019-09-27 15:24:05 -04:00
yarn add @status-im/subspace
2019-09-03 14:40:19 -04:00
```
## Importing the library
```js
// ESM (might require babel / browserify)
2019-09-27 15:24:05 -04:00
import Subspace from '@status-im/subspace';
2019-09-03 14:40:19 -04:00
// CommonJS
2019-09-27 15:24:05 -04:00
const Subspace = require('@status-im/subspace');
2019-09-03 14:40:19 -04:00
```
## Connecting to a web3 provider
2019-09-11 10:07:10 -04:00
To interact with the EVM, **Subspace** requires a valid websockets Web3 provider.
2019-09-03 14:40:19 -04:00
```js
2019-09-27 15:24:05 -04:00
const subspace = new Subspace(web3.currentProvider);
await subspace.init();
2019-09-03 14:40:19 -04:00
```
2019-09-11 10:07:10 -04:00
In addition to the provider, `Subspace` also accepts an `options` object with settings that can change its behavior:
- `dbFilename` - Name of the database where the information will be stored (default `'subspace.db'`)
2019-09-06 09:28:26 -04:00
- `callInterval` - Interval of time in milliseconds to query a contract/address to determine changes in state or balance (default: `undefined`. Obtains data every block).
2019-09-03 14:40:19 -04:00
## Reacting to data
2019-09-11 10:07:10 -04:00
Once it's initialized, you can use **Subspace**'s methods to track the contract state, events and balances. These functions return RxJS Observables which you can subscribe to, and obtain and transform the observed data via operators.
2019-09-03 14:40:19 -04:00
2019-09-06 09:53:21 -04:00
::: tip What is an Observable?
The `Observable` type can be used to model push-based data sources such as DOM events, timer intervals, and sockets. In addition, observables are:
- Compositional: Observables can be composed with higher-order combinators.
- Lazy: Observables do not start emitting data until an observer has subscribed.
:::
2019-09-03 14:40:19 -04:00
2019-09-09 19:49:35 -04:00
#### Further read
- [RxJS Observables](https://rxjs-dev.firebaseapp.com/guide/observable)
## Tracking state
You can track changes to a contract state variable, by specifying the view function and arguments to call and query the contract.
2019-09-03 14:40:19 -04:00
```js
const stateObservable$ = Contract.methods.functionName().track();
2019-09-03 14:40:19 -04:00
```
2019-09-06 09:28:26 -04:00
::: tip Tracking the public variables of a contract
State variables implicity create a `view` function when they're defined as `public`. The `functionName` would be the same as the variable name, and `functionArgs` would have a value when the type is a `mapping` or `array` (since these require an index value to query them).
:::
2019-09-03 14:40:19 -04:00
Example:
2019-09-03 14:40:19 -04:00
```js
const productTitle$ = ProductList.methods.products(0).track().map("title");
productTitle$.subscribe((title) => console.log("product title is " + title));
```
The subscriber will be triggered whenever the title changes
## Tracking events
2019-09-03 14:40:19 -04:00
You can track events and react to their returned values.
```js
const eventObservable$ = Contract.event.eventName().track();
```
2019-09-03 14:40:19 -04:00
Example:
2019-09-06 09:28:26 -04:00
```js
const rating$ = Product.events.Rating().track().map("rating")).pipe(map(x => parseInt(x)));
rating$.subscribe((rating) => console.log("rating received: " + rating));
2019-09-03 14:40:19 -04:00
```
**Event Sourcing**
You can easily do event sourcing with subspace.
2019-09-03 14:40:19 -04:00
For e.g: if you needed to get the average rating of the last 5 events:
```js
import { $average, $latest } from "@status-im/subspace";
2019-09-03 14:40:19 -04:00
const rating$ = Product.events.Rating().track().map("rating")).pipe(map(x => parseInt(x)));
rating$.pipe($latest(5), $average()).subscribe((rating) => {
console.log("average rating of the last 5 events is " + rating)
});
```
## Tracking balances
2019-09-06 09:28:26 -04:00
You can also track changes in both ETH and ERC20 token balances for each mined block or time interval depending on the `callInterval` configured.
2019-09-03 14:40:19 -04:00
Tracking ETH balance in an address:
2019-09-03 14:40:19 -04:00
```js
const address = "0x0001020304050607080900010203040506070809";
subspace.trackBalance(address).subscribe((balance) => {
console.log("ETH balance is ", balance)
});
2019-09-03 14:40:19 -04:00
```
Tracking ETH balance in a Contract:
```js
Contract.trackBalance().subscribe((balance) => {
console.log("ETH balance is ", balance)
});
```
Tracking an ERC20 balance in a Contract:
2019-09-03 14:40:19 -04:00
```js
const tokenAddress = "0x744d70fdbe2ba4cf95131626614a1763df805b9e"; // SNT Address
const myBalanceObservable$ = Contract.trackBalance(tokenAddress);
2019-09-03 14:40:19 -04:00
```
2019-09-06 09:53:21 -04:00
::: warning
2019-09-06 09:28:26 -04:00
Balances are returned as a string containing the value in *wei*.
:::
2019-09-03 14:40:19 -04:00
## Subscriptions
2019-10-24 10:04:25 -04:00
Once you have an `Observable`, you may receive a stream of data by creating a subscription. Subscriptions are triggered each time an observable emits a new value. These subscription receive a callback that must have a parameter which represents the value received from the observable (a contract state variable, an event, or the balance of an address); and they return an object representing the subscription.
2019-09-03 14:40:19 -04:00
Subscriptions can be disposed by executing the method `unsubscribe()` liberating the resource held by it:
```js
2019-09-27 15:24:05 -04:00
const myBalanceObservable$ = subspace.trackBalance(address, tokenAddress);
2019-09-06 09:28:26 -04:00
const subscription = myBalanceObservable$.subscribe(value => {
console.log("The balance is: ", value);
});
2019-09-03 14:40:19 -04:00
// ...
subscription.unsubscribe();
```
2019-09-06 09:28:26 -04:00
#### Further read
- [RxJS Subscriptions](https://rxjs-dev.firebaseapp.com/guide/subscription)
## Cleanup
2019-09-11 10:07:10 -04:00
If **Subspace** is not needed anymore, you need can invoke `close()` to dispose and perform the cleanup necessary to remove the internal subscriptions and interval timers created by **Subspace** during its normal execution, thus avoiding any potential memory leak.
2019-09-09 19:49:35 -04:00
2019-09-03 14:40:19 -04:00
```
2019-09-27 15:24:05 -04:00
subspace.close();
2019-09-03 14:40:19 -04:00
```
2019-09-06 09:53:21 -04:00
::: warning What about subscriptions created with our observables?
2019-09-06 09:28:26 -04:00
Any subscription created via the tracking methods must be unsubscribed manually (in the current version).
:::
2019-09-03 14:40:19 -04:00