Thank you for considering contributing to the Const Type Args framework! We welcome all types of contributions, including bug reports, feature requests, code contributions, documentation improvements, and other contributions.
Please take a moment to read through this document to ensure your contribution is smooth and helpful to the project.
Please note that this project is governed by the Code of Conduct. By participating, you agree to abide by its terms.
This project has adopted the .NET Foundation Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
There are several ways to contribute to the project:
- Reporting Bugs
- Requesting Features
- Submitting Code
- Improving Documentation
- Reviewing Pull Requests
We value every contribution, whether it's code or feedback!
If you encounter a bug in the framework, please:
-
Check Existing Issues: Search the issues to see if the bug has already been reported.
-
Submit a New Issue: If the bug hasn’t been reported, submit a new issue. Include as much detail as possible, including:
- Steps to reproduce the bug
- Expected behavior
- Actual behavior
- Environment details (e.g., .NET version, OS)
We welcome feature requests! If you have an idea for a feature, please:
-
Search Existing Discussions: Search the discussions to make sure your feature hasn’t already been requested.
-
Submit a New Feature Request: If your feature doesn’t exist, open a new discussion. Describe the feature, its use case, and why you think it would benefit the project.
We highly value documentation contributions. Here’s how you can help:
- Update DocFX documentation site.
- Improve READMEs. If you find the README lacking in any way, please submit a pull request with your improvements.
- Fix typos or grammar issues.
- Contribute to API documentation using XML comments in the code.
By contributing to the Const Type Args framework, you agree that your contributions will be licensed under the project's MIT License.
Contributions must not contain breaking changes such as backward incompatible modification of API signatures. The only exception is a new major version of the library. However, it should pass through code review and discussion.