@wireio/core

JavaScript library for working with Wire powered blockchains (formerly EOSIO, still compatible with EOSIO).

Avaiable on npm:

Install

``sh npm install @wireio/core`

`API Documentation`

- API Documentation

`Documentation`

Tests provide good reference material on how to do nearly everything.

More:

- Using APIs: - Serialization: - Crypto Operations: - Primitive Data Types:

`Reporting Issues`

If you think you've found an issue with this codebase, please submit a pull request with a failing unit test to better help us reproduce and understand the issue you are experiencing.

To do this, fork this repository and create your own branch. In this new branch, use the test scaffolding at the path below to write code that either fails to execute, throws an error, or doesn't return the anticipated response.

`sh ./test/bug-report.ts`

This specific test can be run within the root project folder either using make:

`bash grep="bug-report" make test`

Or running mocha directly from the installed ./node_modules folder:

`bash TS_NODE_PROJECT='./test/tsconfig.json' ./node_modules/.bin/mocha -u tdd -r ts-node/register -r tsconfig-paths/register --extension ts test/*.ts --grep="bug-report"`

Once your test is failing and successfully shows the issue occurring, please submit a pull request to this repository. Feel free to include any additional details in the body of the pull request that might help us understand the situation.

> NOTE: If you are performing API requests from within unit tests, you will need to prepend MOCK_RECORD=true to the above commands in order instruct the test running to execute and cache the API request. Any subsequent API requests will utilize this cache to prevent the test from continously accessing API endpoints. Prefixing your command with MOCK_RECORD=overwrite is also possible which forces the test to ignore the cache and fetch new data.

`Running Tests`

`$3`

`sh make test`

`$3`

`sh make coverage``

Debugging

Instructions and notes on debugging typescript in your IDE. Explains how to match the Mocha test configuration found in the Makefile.

Notes on setting up IDE Debuggers

License

FSL-1.1-Apache-2.0

Reporting Issues

If you think you've found an issue with this codebase, please submit a pull request with a failing unit test to better help us reproduce and understand the issue you are experiencing.

To do this, fork this repository and create your own branch. In this new branch, use the test scaffolding at the path below to write code that either fails to execute, throws an error, or doesn't return the anticipated response.

sh
./test/bug-report.ts

This specific test can be run within the root project folder either using make:

bash
grep="bug-report" make test

Or running mocha directly from the installed ./node_modules folder:

bash
TS_NODE_PROJECT='./test/tsconfig.json' ./node_modules/.bin/mocha -u tdd -r ts-node/register -r tsconfig-paths/register --extension ts test/*.ts --grep="bug-report"

Once your test is failing and successfully shows the issue occurring, please submit a pull request to this repository. Feel free to include any additional details in the body of the pull request that might help us understand the situation.

> NOTE: If you are performing API requests from within unit tests, you will need to prepend MOCK_RECORD=true

 to the above commands in order instruct the test running to execute and cache the API request. Any subsequent API requests will utilize this cache to prevent the test from continously accessing API endpoints. Prefixing your command with

MOCK_RECORD=overwrite is also possible which forces the test to ignore the cache and fetch new data.