@myria/api-request
v0.0.2-alpha
Published
Myria's Typescript api-request
Downloads
322
Readme
api-request
Let Myria's clients who is going to interact with L2 service to reuse our built-in base api service.
Prerequisites
The following tools need to be installed:
How to use
Install
# via npmjs
npm i @myria/api-request
# via github on main branch
npm i "https://github.com/myria-libs/api-request.git#main"
Consume
Reference the implementation on example/src/index.ts
How to contribute
Install dependencies and build it
# reinitialize existing Git repository
git init
# install dependencies
npm install | yarn install
# run build
npm run build | yarn build
Verify or fix lint
# check lint's rules
npm run lint | yarn lint
# check lint's rules and try to fix
npm run lint:fix | yarn lint:fix
# format your code
npm run prettier:format | yarn prettier:format
Verify unit test
npm test | yarn test
Collaboration
- We use the git rebase strategy to keep tracking meaningful commit message. Help to enable rebase when pull
$ git config --local pull.rebase true
- Follow TypeScript Style Guide Google
- Follow Best-Practices in coding:
- Clean code make team happy
- Return early make code safer and use resource Efficiency
- Truthy & Falsy make code shorter
- SOLID Principles make clean code
- DRY & KISS avoid redundancy and make your code as simple as possible
- Make buildable commit and pull latest code from
main
branch frequently - Follow the Semantic Versioning once we are ready for release
- Use readable commit message karma to let us use it in the release notes
/‾‾‾‾‾‾‾‾
🔔 < Ring! Please use semantic commit messages
\________
<type>(<scope>): ([issue number]) <subject>
│ │ | │
| | | └─> subject in present tense. Not capitalized. No period at the end.
| | |
│ │ └─> Issue number (optional): Jira Ticket or Issue number
│ │
│ └─> Scope (optional): eg. Articles, Profile, Core
│
└─> Type: chore, docs, feat, fix, refactor, style, ci, perf, build, or test.