Skip to content
Sample app demonstrating use of the DIF Identity Hub JavaScript SDK.
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode Initial commit of sample app. Feb 27, 2019
assets Initial commit of sample app. Feb 27, 2019
src Initial commit of sample app. Feb 27, 2019
.gitignore Initial commit of sample app. Feb 27, 2019
.travis.yml Add Travis CI config. (#1) Feb 27, 2019
LICENSE Initial commit of sample app. Feb 27, 2019
README.md Initial commit of sample app. Feb 27, 2019
index.html Initial commit of sample app. Feb 27, 2019
package-lock.json Update did-common-typescript to 0.1.7. (#2) Mar 20, 2019
package.json
tsconfig.json Initial commit of sample app. Feb 27, 2019
tslint.json Initial commit of sample app. Feb 27, 2019

README.md

DIF Logo

Identity Hub JavaScript SDK Sample

This repository contains a sample app using the DIF Identity Hub JavaScript SDK.

For more details about the APIs used, see the Hub SDK API Reference.

Running the sample app

To run the sample app, clone this repository locally and then run:

npm install
npm run build
npm run start

How it works

The sample app stores objects representing to-do items in your Hub:

  1. When you add a new to-do, the app authors a create commit to instantiate a new object and issues a HubWriteRequest to commit the operation to your Hub.

  2. When you change the done state of a to-do, the app authors an update commit. This commit references the object_id of the to-do and contains the updated to-do state. The app then issues a HubWriteRequest to commit the update operation to your Hub.

  3. When you delete a to-do, the app authors a delete commit referencing the object_id of the to-do and issues a HubWriteRequest to commit the delete operation to your Hub.

  4. When you close and re-open the app, the app fetches any existing to-dos from your Hub. The app issues a HubObjectQueryRequest to identify the object_ids of all objects having the to-do schema. The app then issues a HubCommitQueryRequest to retrieve the constituent commits of all of the identified objects. Once all commits are retrieved, the app uses the CommitStrategyBasic strategy to compile the commits into the final state of each to-do.

The code interacting with the Hub JS SDK is mostly found in the src/HubStore.ts file.

You can’t perform that action at this time.