-
Notifications
You must be signed in to change notification settings - Fork 60
Contributing
Michael Ketting edited this page Nov 5, 2017
·
1 revision
Contributions to re-linq must follow the following guidelines in order to keep up the standards and quality of re-linq:
- Integration tests must be provided in UnitTests/Parsing/QueryParserIntegrationTests
- The integration tests check that the LINQ-query corresponds to the expected expression tree
- The coding style and formatting must follow the setup shown in the rest of re-linq. To help with this, a ReSharper settings file is part of the project.
- New files are fitted with a license header. This is usually done automatically via LicenseHeaderManager
- There must be unit tests written in test first (or at least, be indistinguishable from a test first approach) for each change to the library code.
- Public and protected members must provide argument checks (see existing code). Simple argument checks (e.g. not-null or string-not-empty) are not explictly tested.
re-linq is available under the Apache Software License (SAL) v2.0. First-time contributors are asked to sign a Contributor Assignment Agreement.