First off, thank you for considering contributing to ProImageEditor! Your support helps make this project better for everyone.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project, you agree to abide by its terms.
If you encounter a bug, please report it by opening a bug report. The bug report template will guide you to provide the necessary details, such as:
- Steps to reproduce the issue.
- Expected and actual behavior.
- Screenshots or code snippets.
- Environment details (e.g., OS, Flutter version, etc.).
We welcome suggestions to improve ProImageEditor! To propose an enhancement, open a feature request. The feature request template includes fields for:
- A description of the proposed enhancement.
- The problem it solves or the benefit it provides.
- Any relevant examples, mockups, or use cases.
To contribute code:
- Fork the repository.
- Create a new branch (
git checkout -b feature/YourFeatureName
). - Make your changes, ensuring they adhere to the project's coding standards.
- Run
dart analyze
to ensure no static analysis issues. - Run
flutter test
to ensure all tests pass. - Commit your changes with a conventional git commit.
- Push to your forked repository (
git push origin feature/YourFeatureName
). - Open a pull request against the
stable
branch.
In your pull request:
- Reference any related issues.
- Provide a clear description of the changes and their purpose.
- Highlight any areas that may need special attention during review.
To set up a local development environment:
- Ensure you have Flutter installed.
- Clone the repository:
git clone https://github.com/hm21/pro_image_editor.git
- Navigate to the project directory:
cd pro_image_editor
- Install dependencies:
flutter pub get
- Run the example app to test:
flutter run
We use conventional commits for commit messages. Please follow this format: <type>(scope): <subject>
Examples:
feat(editor): add new filter options
fix(image_processing): resolve crash on iOS devices
docs(contributing): update contributing guidelines
Valid commit types include:
feat
: A new feature.fix
: A bug fix.docs
: Documentation changes.style
: Code style changes (white-space, formatting, etc.).refactor
: Code refactoring without changing functionality.test
: Adding or updating tests.chore
: Maintenance tasks (e.g., updating dependencies).
- Follow the Dart style guide.
- Use
flutter format
to format your code. - Ensure that
dart analyze
runs without any warnings or errors. - Ensure that
flutter test
passes without failures. - Write documentation comments for public APIs.
Thank you for contributing to ProImageEditor!