We're glad you're interested in contributing to our project! This document provides guidelines for contributing and instructions on how to set up the project locally for development and testing.
- Setting Up the Development Environment
- Running the Extension Locally
- Testing
- Coding Standards
- Submitting Changes
- Reporting Bugs
- Fork the repository on GitHub.
- Clone your forked repository to your local machine:
git clone https://github.com/your-username/fb-marketplace-csv-generator.git
- Navigate to the project directory:
cd fb-marketplace-csv-generator
- Install any necessary dependencies (if applicable):
npm install
- Open Google Chrome and navigate to
chrome://extensions/
. - Enable "Developer mode" in the top right corner.
- Click "Load unpacked" and select the directory containing the extension files.
- The extension should now appear in your Chrome toolbar.
To see your changes after modifying the code:
- Make your changes to the relevant files.
- Go back to the
chrome://extensions/
page. - Find the extension and click the refresh icon.
- If you've made changes to the background script, you may need to click on the "service worker" link to see console logs.
- Click on the extension icon to open the popup.
- Try dragging and dropping different types of image files.
- Test the "Generate CSV" functionality.
- Check the generated CSV file for accuracy.
(Note: Implement automated tests as part of the TODO list)
Once implemented, run the tests using:
npm test
- Follow the existing coding style and conventions used in the project.
- Keep code organized, readable, and maintainable.
- Use meaningful variable names and comments to explain complex logic.
- Create a new branch for your changes:
git checkout -b my-new-feature
- Commit your changes with a descriptive commit message:
git commit -m "Added new feature: [briefly describe the change]"
- Push your branch to your forked repository:
git push origin my-new-feature
- Create a pull request to the main repository.
If you find any bugs or issues with the extension, please open an issue on the GitHub repository with the following information:
- A clear description of the bug or issue.
- Steps to reproduce the bug (if applicable).
- Any relevant error messages or console logs.
We appreciate your contributions and feedback!