Contributing
Thank you for considering contributing to the Leighton API Test Harness! We welcome contributions from the community to help improve this project. Here are some guidelines to help you get started:
Code of Conduct
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.
Getting Started
- Install Node.js (v22.15.1 recommended)
- Clone the repository
- Install dependencies:
npm install
- Run tests:
npm test
Local Development
To test changes to this package locally in another project:
-
Build the package:
npm run build
-
Create a symbolic link:
npm link
-
In your test project:
npm link @leighton-digital/{cloud blocks package name}
-
To remove the link:
npm unlink @leighton-digital/{cloud blocks package name}
Note: Ensure your test project has the same version of Node.js and compatible dependencies.
How to Contribute
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature
) - Commit your changes (
git commit -m 'Add some amazing feature'
) - Push to the branch (
git push origin feature/amazing-feature
) - Open a Pull Request
Code Style
- Follow TypeScript best practices
- Use Biome for linting and formatting
- Write clear commit messages
- Add tests for new features
- Update documentation
Testing Guidelines
We use Jest for testing. Please ensure:
- All existing tests pass
- New features have appropriate tests
Pull Request Process
- Ensure all tests pass:
npm test
- Update the documentation if needed
- Add a clear description of your changes
- Reference any related issues
- Wait for review
- Be prepared to make requested changes
Code of Conduct
Please follow our Code of Conduct in all interactions.
Questions?
If you have any questions about contributing, feel free to open an issue or contact the maintainers.