-
Notifications
You must be signed in to change notification settings - Fork 20
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 #35 from codePerfectPlus/type-check
Updated the fastapi and docs
- Loading branch information
Showing
12 changed files
with
278 additions
and
159 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,34 @@ | ||
# Changelog | ||
|
||
All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | ||
|
||
## Changelog | ||
|
||
## [Unreleased] | ||
|
||
- Moved test files to random_profile to avoid flake8:402 error | ||
- Following proper changelog format, added changelog file | ||
- Added config for readthedocs | ||
|
||
## [v0.2.3] - 13-10-2022 | ||
|
||
- Flask app added | ||
- Date of Birth Added | ||
- Age added | ||
- Height and Weight Added | ||
- Blood Group and hair color added | ||
- Job title added | ||
- More email domains added | ||
- Bugs Fixed | ||
|
||
## [v0.2.1] - 12-10-2022 | ||
|
||
- More variation added to the data | ||
- Test cases added | ||
- Created a separate file for data loadings | ||
- Fixed some bugs | ||
|
||
|
||
## [V0.0.1] - 19-03-2020 | ||
|
||
- Initial Release |
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,76 @@ | ||
# Contributor Covenant Code of Conduct | ||
|
||
## Our Pledge | ||
|
||
In the interest of fostering an open and welcoming environment, we as | ||
contributors and maintainers pledge to making participation in our project and | ||
our community a harassment-free experience for everyone, regardless of age, body | ||
size, disability, ethnicity, sex characteristics, gender identity and expression, | ||
level of experience, education, socio-economic status, nationality, personal | ||
appearance, race, religion, or sexual identity and orientation. | ||
|
||
## Our Standards | ||
|
||
Examples of behavior that contributes to creating a positive environment | ||
include: | ||
|
||
* Using welcoming and inclusive language | ||
* Being respectful of differing viewpoints and experiences | ||
* Gracefully accepting constructive criticism | ||
* Focusing on what is best for the community | ||
* Showing empathy towards other community members | ||
|
||
Examples of unacceptable behavior by participants include: | ||
|
||
* The use of sexualized language or imagery and unwelcome sexual attention or | ||
advances | ||
* Trolling, insulting/derogatory comments, and personal or political attacks | ||
* Public or private harassment | ||
* Publishing others' private information, such as a physical or electronic | ||
address, without explicit permission | ||
* Other conduct which could reasonably be considered inappropriate in a | ||
professional setting | ||
|
||
## Our Responsibilities | ||
|
||
Project maintainers are responsible for clarifying the standards of acceptable | ||
behavior and are expected to take appropriate and fair corrective action in | ||
response to any instances of unacceptable behavior. | ||
|
||
Project maintainers have the right and responsibility to remove, edit, or | ||
reject comments, commits, code, wiki edits, issues, and other contributions | ||
that are not aligned to this Code of Conduct, or to ban temporarily or | ||
permanently any contributor for other behaviors that they deem inappropriate, | ||
threatening, offensive, or harmful. | ||
|
||
## Scope | ||
|
||
This Code of Conduct applies both within project spaces and in public spaces | ||
when an individual is representing the project or its community. Examples of | ||
representing a project or community include using an official project e-mail | ||
address, posting via an official social media account, or acting as an appointed | ||
representative at an online or offline event. Representation of a project may be | ||
further defined and clarified by project maintainers. | ||
|
||
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
reported by contacting the project team at [email protected]. All | ||
complaints will be reviewed and investigated and will result in a response that | ||
is deemed necessary and appropriate to the circumstances. The project team is | ||
obligated to maintain confidentiality with regard to the reporter of an incident. | ||
Further details of specific enforcement policies may be posted separately. | ||
|
||
Project maintainers who do not follow or enforce the Code of Conduct in good | ||
faith may face temporary or permanent repercussions as determined by other | ||
members of the project's leadership. | ||
|
||
## Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, | ||
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html | ||
|
||
[homepage]: https://www.contributor-covenant.org | ||
|
||
For answers to common questions about this code of conduct, see | ||
https://www.contributor-covenant.org/faq |
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,79 @@ | ||
# Contributing to RandomProfileGenerator | ||
|
||
We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's: | ||
|
||
- Reporting a bug | ||
- Discussing the current state of the code | ||
- Submitting a fix | ||
- Proposing new features | ||
- Becoming a maintainer | ||
|
||
## Steps to contribute | ||
|
||
- Comment on the issue you want to work on. Make sure it's not assigned to someone else. | ||
|
||
### Making a PR | ||
|
||
> - Make sure you have been assigned the issue to which you are making a PR. | ||
> - If you make PR before being assigned, It may be labeled `invalid` and closed without merging. | ||
- Fork the repo and clone it on your machine. | ||
- Add a upstream link to main branch in your cloned repo | ||
|
||
```sh | ||
git remote add upstream https://github.com/py-contributors/RandomProfileGenerator.git | ||
``` | ||
|
||
- Keep your cloned repo upto date by pulling from upstream (this will also avoid any merge conflicts while committing new changes) | ||
|
||
```sh | ||
git pull upstream master | ||
``` | ||
|
||
- Create your feature branch | ||
|
||
```sh | ||
git checkout -b <feature-name> | ||
``` | ||
|
||
- Commit all the changes | ||
|
||
```sh | ||
git commit -am "Meaningful commit message" | ||
``` | ||
|
||
- Push the changes for review | ||
|
||
```sh | ||
git push origin <branch-name> | ||
``` | ||
|
||
- Create a PR from our repo on Github. | ||
|
||
### Additional Notes | ||
|
||
- Any changes should be made in the `dev` branch. | ||
- Changes should be logged in the `CHANGELOG.md` file. | ||
- Code should be properly commented to ensure it's readability. | ||
- If you've added code that should be tested, add tests as comments. | ||
- Make sure your code properly formatted. | ||
- Issue that pull request! | ||
|
||
## Issue suggestions/Bug reporting | ||
|
||
When you are creating an issue, make sure it's not already present. Furthermore, provide a proper description of the changes. If you are suggesting any code improvements, provide through details about the improvements. | ||
**Great Issue suggestions** tend to have: | ||
- A quick summary of the changes. | ||
- In case of any bug provide steps to reproduce | ||
- Be specific! | ||
- Give sample code if you can. | ||
- What you expected would happen | ||
- What actually happens | ||
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work) | ||
|
||
|
||
## License | ||
|
||
By contributing, you agree that your contributions will be licensed under its [MIT License](http://choosealicense.com/licenses/mit/). |
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 was deleted.
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
Oops, something went wrong.