-
Ensure the bug was not already reported by searching on GitHub under Issues.
-
If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
-
Open a new GitHub pull request with the patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of zUIx will generally not be accepted unless discussed via the issue tracker.
File a new enhancement issue.
File a new question issue.
This project follows standardjs.com coding rules.
The build script also includes ESLint checks that are mainly based off the
eslint-config-google
.
You may find out that some of these rules are not fully respected in the existing code,
but this will be fixed from time to time.
See the src/README.md file.
Clone zUIx repository and install dependencies:
npm install
Build source and create minified version in ./dist/js
folder:
npm run build
To submit a new release
npm run release <newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease
If for instance current published version is 1.0.6, npm run release patch
will build library, bump version to 1.0.7 and publish it.
if passing CI tests, new release files will be copied to the CDN website (./docs
folder) and the version number in the README.md
file will be updated.
Also the new API data files will be updated in the ./docs/api
folder.
The script run on the CI server side is
npm run deploy
zUIx is a volunteer effort. We encourage you to pitch in and join the team!
Thanks! ❤️