- The custom event business logic need to be wrapped to a function and be reused
- Components or functions need to be save in a library that others can keep maintaining
- Documentation and Experimental
- Accelerated custom event development
- Be testable and maintainable
-
Install from github
yarn add https://github.com/17media/vmo-lib.git#latest
-
Use components or hooks with vmo-frontend. See Playground folder for use case
-
copy paste whole components file in template can quickly make custom components. See Template folder
-
Use
yarn remove vmo-lib
&yarn add https://github.com/17media/vmo-lib.git
to reinstall the library
- hooks
- components
- offline
- offlineNormal: no team pk leaderboard, only boards with transition
- offlineTeam: team pk leaderboard without transition but every leaderboards should scroll at the same time
- online
- create a folder or file
- testing hooks if needed
- use playground to create use case for vmo-frontend and e2e testing
- local testing
yarn start
- GitHub pages testing
leave comments when coding (support Markdown!) and it would generate docs automatically.
Here is typedoc guideline
Generate document
yarn doc
where config at typedoc.json
to confirm what options have been loaded:
npx typedoc --showConfig
- Before deploy
Run the following command to make sure build successfully.
yarn build:both
- Build and Deploy TypeDoc & Playground (already include build command)
To run the following command, you need to wait until feature branch successfully merged back to master since that is the correct version you want to deploy. After passing QA test, follow "Release" step to release the version.
yarn deploy:both
git checkout master
git pull
yarn
yarn deploy:lib