👍🎉 First off, thanks for taking the time to contribute! 🎉👍
The following is a set of guidelines for contributing to LetXPath. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
Coding style:
- Use camel case for any variable for functions
- Use the regular function in content and other related files to avoid hoisting problem
- All code must have high-level comments
- The naming convention must be understandable
- Write simple and effective code
- Before committing the code, test it with a minimum of five different application
Checkout code with the following prefixes:
- 📦 NEW: - If it's a new feature (eg., 📦 NEW: -Faker API)
- 👌 IMPROVE: - For local commit and push in the existing work
- 🐛 FIX: - If fixing any bug
- 🐧 UI - If anything related UI improvements or bugs
- 🤖 TEST: - Testing the product
- 📖 DOC: - If any documentations or videos
- 🚀 RELEASE: If everything goes right
Yes! emojis are important. Something missing feel free to add
- Willing to contribute
- Knowledge on JavaScript is very important
- Knowledge of XPath pattern
- Knowledge on DOM traversal
Anyone can contribute to our project in four ways
- By developing the XPath pattern
- By designing the UI
- By testing and reporting to us
- The most important by sharing to the world
I don't know how does it work, but I like to contribute. What should I do next?
No worries LetCode has created all the basic video on how to build LetXPath Feel free to check out our get started videos and we appreciate your contribution