-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2 from pachecoio/feature/example-query
Feature/example query
- Loading branch information
Showing
11 changed files
with
818 additions
and
379 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
## CONTRIBUTING.md | ||
|
||
### Welcome to the OpenAPI Mocker Contributing Guide! | ||
|
||
Thank you for your interest in contributing to the OpenAPI Mocker project! We're glad you're here. This document provides guidelines for making contributions to the project. Whether you're looking to submit a bug report, propose new features, or contribute code, your help is very much appreciated. | ||
|
||
### How to Contribute | ||
|
||
#### Reporting Bugs | ||
|
||
Bugs are tracked as GitHub issues. To report a bug, create an issue and include: | ||
|
||
- A clear title and description. | ||
- Steps to reproduce. | ||
- Expected behavior. | ||
- Actual behavior. | ||
- Screenshots if applicable. | ||
|
||
#### Suggesting Enhancements | ||
|
||
We love to receive suggestions for improvements! If you have ideas to make OpenAPI Mocker better, please submit an issue with the following: | ||
|
||
- A clear title and description. | ||
- Explain why this enhancement would be useful to most OpenAPI Mocker users. | ||
- Provide a step-by-step description of the suggested enhancement in as much detail as possible. | ||
|
||
#### Your First Code Contribution | ||
|
||
Unsure where to begin contributing? You can start by looking through the 'beginner' and 'help-wanted' issues: | ||
|
||
- **Beginner issues** - issues which should only require a few lines of code, and a test or two. | ||
- **Help wanted issues** - issues which should be a bit more involved than beginner issues. | ||
|
||
Both issue lists are great places to start and are specifically tagged to indicate that help is needed. | ||
|
||
#### Pull Requests | ||
|
||
Here’s how to submit a pull request: | ||
|
||
1. Fork the repo and create your branch from `main`. | ||
2. Clone the repository to your local machine. | ||
3. Make your changes and ensure your code adheres to the existing style to keep the code consistent. | ||
4. If you've added code, add tests! | ||
5. Ensure your code passes all the tests. | ||
6. Issue that pull request! | ||
|
||
Include a clear description of the reasons for your changes. It should include relevant motivations and context. List any dependencies that are required for this change. | ||
|
||
### Styleguides | ||
|
||
#### Git Commit Messages | ||
|
||
- Use the present tense ("Add feature" not "Added feature"). | ||
- Use the imperative mood ("Move cursor to..." not "Moves cursor to..."). | ||
- Limit the first line to 72 characters or less. | ||
- Reference issues and pull requests liberally after the first line. | ||
|
||
#### Code Style for rust | ||
|
||
- Follow the [Rust style guide](https://doc.rust-lang.org/1.0.0/style/README.html) for Rust code. | ||
- Ensure you run lint checks before submitting your pull request. | ||
|
||
### Community | ||
|
||
- If you have any questions about how to interpret the guidelines or want to discuss a substantial change/idea, don’t hesitate to post on our community channels or directly on GitHub issues. | ||
|
||
### Thank You! | ||
|
||
Every contribution counts, and by participating, you are expected to uphold this code. We appreciate your effort, and are excited to welcome you aboard and see what you can bring to the project! | ||
|
||
Let's create something amazing together! |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
pub mod spec; |
Oops, something went wrong.