Contributing to datatables.mark.js
These are the contributing guidelines of datatables.mark.js. If you are interested in contributing to mark.js itself, please head over to the mark.js repository.
If you have a question, problem, feature request or found a bug please open an issue.
1.1 Questions, Problems and Bugs
For each issue please provide:
- What kind of browser and version you are using
- What kind of mark.js version you are using
- A detailed description
- The exact steps to reproduce (bugs and problems)
- A fiddle that demonstrates your issue (if possible)
1.2 Feature Requests
Please provide the following information:
- Your use case, why your enhancement is necessary
- How to solve it in your opinion
Before you start developing, you should clone or download this repository and run:
$ bower install && npm install
Now you are ready to develop.
2.2 Source Code Documentation
JSDOC is being used as an API documentation generator. If you want to extend this plugin it might be helpful for you to view the documentation first, to learn more about the internal structure. Simply run:
$ grunt dist
and open the file
2.3 ES6 (ES2015) Information
datatables.mark.js was developed in ECMAScript 6. But as most browsers don't fully support ES6 yet, it has only those features implemented that can be converted "locally" to ES5 using Babel without making a polyfill necessary. This means to forgo using generators, Set, Map, for...of loops etc..
2.4 Grunt Tasks
|dev||For development. Will run
|compile||Generates all files in
|lint||Runs ESLint lint|
|test||Runs the test,
Note: Run tasks with
$ grunt [task] (Replace "[task]" with the actual task name).
2.5 Pull Requests
Pull requests are very much appreciated!
Please note the following things when doing a pull request:
- Do not change any version
- Add a test if possible
- Reference related issues in the pull request description
- Describe your changes and why they are necessary (if not stated in referenced issues)
- When changing the code, please run
$ grunt distat the end to generate files in
- Make sure that you format code to fit the code style
2.6 Contribution and License Agreement
If you contribute to this project, you are implicitly allowing your code to be distributed under this license. You are also implicitly verifying that all code is your original work.
Thank you for contributing!