UAL Renderer for react17

This library provides a React renderer around the Universal Authenticator Library.

About EOSIO Labs

EOSIO Labs repositories are experimental. Developers in the community are encouraged to use EOSIO Labs repositories as the basis for code and concepts to incorporate into their applications. Community members are also welcome to contribute and further develop these repositories. Since these repositories are not supported by Block.one, we may not provide responses to issue reports, pull requests, updates to functionality, or other requests from the community, and we encourage the community to take responsibility for these.

Getting Started

With yarn

yarn add ual-react17-renderer

Then, install the authenticators that you wish to use...

yarn add ual-scatter ual-lynx

With npm

npm i ual-react17-renderer

Then, install the authenticators that you wish to use...

npm i ual-scatter ual-lynx

Basic Usage

import React from 'react'
import ReactDOM from 'react-dom'
import { UALProvider, withUAL } from 'ual-react17-renderer'
import { Scatter } from 'ual-scatter'
import { Lynx } from 'ual-lynx'

import { MyApp } from './MyApp'

const myChain = {
  chainId: MY_CHAIN_ID,
  rpcEndpoints: [{
    protocol: MY_CHAIN_PROTOCOL,
    host: MY_CHAIN_HOST,
    port: MY_CHAIN_PORT,
  }]
}

const scatter = new Scatter([myChain], { appName: 'My App' })
const lynx = new Lynx([myChain], { appName: 'My App' })

const MyUALConsumer = withUAL(MyApp)

ReactDOM.render(
  <UALProvider chains={[myChain]} authenticators={[scatter, lynx]} appName={'My App'}>
    <MyUALConsumer />
  </UALProvider>,
  document.getElementById('ual-app')
)

Examples

A small example is provided in the examples folder.

Environment Set Up

A one-time environment setup is required prior to development. The following commands provides a quick starting point. Make sure you are in the examples/ directory.

cd examples
cp default.env .env

Now that you have an .env file, you can set environment variables for your chain particulars. Note that this file will not be version-controlled, nor should it be. The default settings for the file are...

CHAIN_ID=cf057bbfb72640471fd910bcb67639c22df9f92470936cddc1ade0e2f2e7dc4f
RPC_PROTOCOL=http
RPC_HOST=localhost
RPC_PORT=8888

These values are taken from the local chain created by following the Developer Portal node set up instructions. (Note: if this is your first time following the tutorial you will need to install the eosio binaries here) These can be edited according to the requirements of your project if you have a different chain set up. They will be used as the chain data in the example app. See the Basic Example App for UAL with react17 for more details.

Development

After you set up your environment you can begin development. Make sure you are back in the / directory of the ual-react17-renderer package.

yarn
yarn link
yarn build -w

In a duplicate terminal tab, enter the following commands:

cd examples
yarn link ual-react17-renderer
yarn
yarn example

Open a browser at localhost:3000 to see a running instance of the example.

It is recommended to have at least two terminal tabs running so that yarn build -w and yarn example can run simultaneously creating an environment where changes are immediately reflected in the browser.

Contributing

Contributing Guide

Code of Conduct

License

MIT

Important

See LICENSE for copyright and license terms.

The MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.