Blade Labs Documentation
Dapp Integration
Blade SDKWeb App SDK (for Browser based Apps)Kotlin Blade for AndroidSwift Blade SDK for iOSCPP Blade SDKCPP Demo AppBlade Wallet Demo App"Connect with Blade" integrationBlade AirdropBlade-nft-buttonDapp IntegrationUnity Blade SDKReact Native Blade SDK
Dapp Integration
Blade SDKWeb App SDK (for Browser based Apps)Kotlin Blade for AndroidSwift Blade SDK for iOSCPP Blade SDKCPP Demo AppBlade Wallet Demo App"Connect with Blade" integrationBlade AirdropBlade-nft-buttonDapp IntegrationUnity Blade SDKReact Native Blade SDK
  • README
  • CHANGELOG
  • CONTRIBUTING
Powered by GitBook
On this page
  • Creating releases
  • Reference

CONTRIBUTING

PreviousCHANGELOG

Last updated 1 year ago

Thanks for contributing to blade-web3.js!

As a contributor, here are the guidelines we would like you to follow:

  • Ensure npm build runs without errors before submitting a Pull Request

  • Features and bug fixes should be covered by new test cases

  • Commits follow the

Creating releases

We use to release new versions from the master branch:

  • Commits of type fix will trigger bugfix releases, think 0.0.1

  • Commits of type feat will trigger feature releases, think 0.1.0

  • Commits with BREAKING CHANGE in body or footer will trigger breaking releases, think 1.0.0

All other commit types will not result in a new release.

Reference

Static Analysis

tslint and TypeScript are used.

API Documentation

TypeDoc is used to document the public API. See https://typedoc.org/ for details.

Angular commit convention
semantic-release