@myria/redis-js

redis-js

Interact with redis cache follow CQRS pattern

Prerequisites

The following tools need to be installed:

1. Git
2. Node.js 20+

Capabilities and Frameworks

Capability	Module
Coding Standard	eslint statically analyzes your code to quickly find and fix problems based on opt-in rules, prettier an opinionated code formatter to build and enforce a style guide on save, eslint-config-prettier to turns off all rules that are unnecessary or might conflict with Prettier.
Testing Framework	Jest a delightful JavaScript Testing Framework with a focus on simplicity.
Useful Links	npmtrends Compare package download counts over time, act run your GitHub Actions locally, Actionlint static checker for GitHub Actions workflow files,TypeDoc is a documentation generator for TypeScript

How to

Clone and run build

git clone [e-mail]:myria-libs/redis-js.git
# install dependencies
npm install | yarn install
# run build
npm run build | yarn build

Run 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

Run test

npm test | yarn test

Integration

import { RedisService, Config } from '@myria/redis-js';

(function () {
    const config = new Config({
        redisHost: 'localhost',
        redisPort: 6379,
        redisReplicaHost: 'localhost',
        isEnableRedisTLS: false,
        redisPassword: "localhost"
    })
    const redisService = RedisService.getInstance(config);
})();

Full E2E integration reference in the example/src/index.js. Should be straightforward

Collaboration

1. We use the git rebase strategy to keep tracking meaningful commit message. Help to enable rebase when pull $ git config --local pull.rebase true
2. Follow TypeScript Style Guide Google
3. Follow Best-Practices in coding:
   1. Clean code make team happy
   2. Return early make code safer and use resource Efficiency
   3. Truthy & Falsy make code shorter
   4. SOLID Principles make clean code
   5. DRY & KISS avoid redundancy and make your code as simple as possible
4. Make buildable commit and pull latest code from main branch frequently
5. Follow the Semantic Versioning once we are ready for release
6. Use readable commit message karma

     /‾‾‾‾‾‾‾‾
🔔  <  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.