Files
nym/clients/validator
Dave Hrycyszyn f6a79ce7c3 Renaming validator-api to nym-api (#1863)
* Renaming validator-api to nym-api

* nym-api: simplified crate name

* Added nym-api rename to changelog

* Changed some output messages

* Renamed validator-api-requests to nym-api requests

* Removing more references to validator-api-requests

* Additional lockfile name changes after full build

* Removing mistakenly added merge files

* ibid

* ibid

* Getting rid of ref to validator_api deep inside validator-client

* Fixing file storage paths

* Renaming struct function names referring to validator_api

* Simplifying struct init

* Fixed up all other instances of nym_api.

* Renaming validatorApi to nymApi in TypeScript client for consistency

v

* Found a few more Rust instances

* Changed examples in TypeScript SDK

* Found one more instance of the use of validator instead of nym apis

* Aliasing config key name for deserialization to preserve compatibility with old configs
2022-12-14 15:05:01 +00:00
..
2021-12-16 15:35:30 +00:00
2021-03-24 11:49:58 +00:00
2021-12-16 15:35:30 +00:00
2021-03-24 11:49:58 +00:00

Nym Validator Client

A TypeScript client for interacting with CosmWasm smart contracts in Nym validators.

Running examples

With the code checked out, cd examples. This folder contains runnable example code that will set up a blockchain and allow you to interact with it through the client.

Running tests

npm test

You can also trigger test execution with a test watcher. I don't have the centuries of life left to me that are needed to fight through the arcana of wiring up a working TypeScript mocha triggered execution setup, so for now my Cargo-based hack is:

cargo watch -s "cd clients/validator && npm test"

It's ugly but works fine if you have Cargo installed. TypeScript setup help happily accepted here.

Generating Documentation

You can generate docs by running npm run docs. Generated output will appear in the docs directory.

Packaging

If you're a Nym platform developer who's made changes to the client and wants to re-publish the package to NPM, here's how you do it:

  1. Bump the version number (use SemVer)
  2. npm run build
  3. npm login (if you haven't already)
  4. npm publish