|
| 1 | +# Contributing to React Scan |
| 2 | + |
| 3 | +First off, thanks for taking the time to contribute! ❤️ |
| 4 | + |
| 5 | +## Table of Contents |
| 6 | + |
| 7 | +- [Contributing to React Scan](#contributing-to-react-scan) |
| 8 | + - [Table of Contents](#table-of-contents) |
| 9 | + - [Project Structure](#project-structure) |
| 10 | + - [Development Setup](#development-setup) |
| 11 | + - [Contributing Guidelines](#contributing-guidelines) |
| 12 | + - [Commits](#commits) |
| 13 | + - [Pull Request Process](#pull-request-process) |
| 14 | + - [Development Workflow](#development-workflow) |
| 15 | + - [Getting Help](#getting-help) |
| 16 | + |
| 17 | +## Project Structure |
| 18 | + |
| 19 | +This is a monorepo containing several packages: |
| 20 | + |
| 21 | +- `packages/scan` - Core React Scan package |
| 22 | +- `packages/vite-plugin-react-scan` - Vite plugin for React Scan |
| 23 | +- `packages/extension` - VS Code extension |
| 24 | + |
| 25 | +## Development Setup |
| 26 | + |
| 27 | +1. **Clone and Install** |
| 28 | + ```bash |
| 29 | + git clone https://github.com/aidenybai/react-scan.git |
| 30 | + cd react-scan |
| 31 | + pnpm install |
| 32 | + ``` |
| 33 | + |
| 34 | +2. **Build all packages** |
| 35 | + ```bash |
| 36 | + pnpm build |
| 37 | + ``` |
| 38 | + |
| 39 | +3. **Development Mode** |
| 40 | + ```bash |
| 41 | + # Run all packages in dev mode |
| 42 | + pnpm dev |
| 43 | + ``` |
| 44 | + |
| 45 | +## Contributing Guidelines |
| 46 | + |
| 47 | +### Commits |
| 48 | + |
| 49 | +We use conventional commits to ensure consistent commit messages: |
| 50 | + |
| 51 | +- `feat:` New features |
| 52 | +- `fix:` Bug fixes |
| 53 | +- `docs:` Documentation changes |
| 54 | +- `chore:` Maintenance tasks |
| 55 | +- `test:` Adding or updating tests |
| 56 | +- `refactor:` Code changes that neither fix bugs nor add features |
| 57 | + |
| 58 | +Example: `fix(scan): fix a typo` |
| 59 | + |
| 60 | +### Pull Request Process |
| 61 | + |
| 62 | +1. Fork the repository |
| 63 | +2. Create your feature branch (`git checkout -b feat/amazing-feature`) |
| 64 | +3. Commit your changes using conventional commits |
| 65 | +4. Push to your branch |
| 66 | +5. Open a Pull Request |
| 67 | +6. Ask for reviews (@pivanov, @RobPruzan are your friends in this journey) |
| 68 | + |
| 69 | +### Development Workflow |
| 70 | + |
| 71 | +1. **TypeScript** |
| 72 | + - All code must be written in TypeScript |
| 73 | + - Ensure strict type checking passes |
| 74 | + - No `any` types unless absolutely necessary |
| 75 | + |
| 76 | +2. **Code Style** |
| 77 | + - We use Biome for formatting and linting |
| 78 | + - Run `pnpm format` to format code |
| 79 | + - Run `pnpm lint` to check for issues |
| 80 | + |
| 81 | +3. **Documentation** |
| 82 | + - Update relevant documentation |
| 83 | + - Add JSDoc comments for public APIs |
| 84 | + - Update README if needed |
| 85 | + |
| 86 | +## Getting Help |
| 87 | +- Check existing issues |
| 88 | +- Create a new issue |
| 89 | + |
| 90 | +<br /> |
| 91 | + |
| 92 | +⚛️ Happy coding! 🚀 |
0 commit comments