UNPKG

@iyonger/aptos-web3-bip44.js

Version:
47 lines (23 loc) 1.68 kB
* **Please check if the PR fulfills these requirements** - [ ] Tests for the changes have been added (for bug fixes/features) - [ ] Docs have been added / updated (for bug fixes / features) * **What kind of change does this PR introduce?** (Bug fix, feature, docs update, ...) * **What is the current behavior?** (You can also link to an open issue here/ Jira tasks) * **What is the new behavior (if this is a feature change)?** * **What are the testcases and how have you tested them** * **Does this PR introduce a breaking change?** (What changes might users need to make in their application due to this PR?) * **Other information**: * * **Note**: Please, go through these steps before you submit a PR. 1. Make sure that your PR is not a duplicate. 2. If not, then make sure that: a. You have done your changes in a separate branch. Branches MUST have descriptive names that start with either the `fix/` or `feature/` prefixes. Good examples are: `fix/signin-issue` or `feature/issue-templates`. b. You have a descriptive commit message with a short title (first line). c. You have only one commit (if not, squash them into one commit). d. `npm test` doesn't throw any error. If it does, fix them first and amend your commit (`git commit --amend`). 3. **After** these steps, you're ready to open a pull request. a. Give a descriptive title to your PR. b. Describe your changes. c. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). IMPORTANT: Please review the [CONTRIBUTING.md](../CONTRIBUTING.md) file for detailed contributing guidelines.