Thanks for helping improve Light.GuardClauses.
- Open an issue before starting a new assertion or substantial change so its API and scope can be discussed.
- Keep each pull request focused on one change and follow the style of the surrounding code.
- Add functional tests for behavior changes. Add or update a benchmark when performance is a relevant risk.
- Build and test the complete solution before submitting the pull request.
The contributor and build guide describes the required SDK, repository layout, build commands, test-framework overrides, assertion conventions, analyzers, benchmarks, and source-export projects.
User-facing guidance belongs under docs. Keep the root README concise and update documentation in the same pull request as the behavior it describes.