First of all, thanks for taking the time to contribute!
- 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.
Please read this page to understand how to get the extension logs. If you don't know how to report bugs effectively, please use this article as a guideline.
- Open a new GitHub pull request with the patch.
- Ensure the PR description clearly describes the problem and solution. Include the relevant issue number(s) if applicable.
It's also worth reading how to write good commit messages.
We use a number of linters to verify the source code. Please ensure before committing the changes they meet our requirements by running grunt lint. If you're not familiar with Grunt, please read this article.
We also use EditorConfig, which helps to keep code in the same code style in different code editors and IDE's. If you haven't use EditorConfig before, you can visit EditorConfig website for further information.
Connectors development is explained in this and this articles.