Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: refactor HTTP error codes for PUT /mentorship_relation/{request_id}/task/{task_id}/comment/{comment_id} #1127

Closed

Conversation

RiddhiAthreya
Copy link
Contributor

Description

Made changes to the HTTP error codes being returned according to what's discussed in the issue. I have also made the appropriate changes in the swagger documentation.

Fixes #634

Type of Change:

  • Code
  • Quality Assurance

Code/Quality Assurance Only

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Screenshot (172)

Screenshot (173)

Checklist:

  • My PR follows the style guidelines of this project
  • I have performed a self-review of my own code or materials
  • Update Swagger documentation

Code/Quality Assurance Only

  • My changes generate no new warnings
  • New and existing unit tests pass locally with my changes

@vj-codes
Copy link
Member

@RiddhiAthreya the linked issue is a first timers only issue, and you have already made your first contribution through #1126. Please check the issue labels while claiming next time :)

@vj-codes vj-codes added the Status: Needs Review PR needs an additional review or a maintainer's review. label Jul 11, 2021
Copy link
Member

@vj-codes vj-codes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RiddhiAthreya please resolve the merge conflicts

@vj-codes vj-codes added Status: Changes Requested Changes are required to be done by the PR author. and removed Status: Needs Review PR needs an additional review or a maintainer's review. labels Jul 24, 2021
Copy link
Member

@devkapilbansal devkapilbansal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RiddhiAthreya I see you remove the changes done for pre-commit. Please revert those changes.

Comment on lines -1 to -6
[flake8]
ignore =
# W503: line break before binary operator
# ignored as it creates inconsistency with black
W503,
# E501: line too long (> 88 characters)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this file is deleted?

This is important for flake8 to work correctly.

@@ -7,16 +7,16 @@
* When developing a new feature, include at least one test when applicable.
* When submitting a PR, please follow [this template](PULL_REQUEST_TEMPLATE.md) (which will probably be already filled up once you create the PR).
* When submitting a PR with changes to user interface (e.g.: new screen, or an email template), please add screenshots to the PR description.
* When you are finished with your work, please squash your commits otherwise we will squash them on your PR (this can help us maintain a clear commit history).
* When you are finished with your work, please squash your commits otherwise we will squash them on your PR (this can help us maintain a clear commit history).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There should not be any space at the end. Trim the whitespace please

* When writing in-code documentation as Docstrings, please follow [this guide](https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings).
* When creating an issue to report a bug in the project, please follow our [bug_report.md](https://github.com/anitab-org/.github/blob/main/.github/ISSUE_TEMPLATE/bug_report.md) template.

## General Guidelines

* If you’re just getting started work on an issue labeled “First Timers Only” in any project. Additional resources are available on our [website](http://www.systers.io).
* In an active repository (not an archived one), choose an open issue from the issue list, claim it in the comments, and a maintainer will assign it to you.
* In an active repository (not an archived one), choose an open issue from the issue list, claim it in the comments, and a maintainer will assign it to you.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above. Same for similar cases as well

@@ -1,9 +0,0 @@
[tool.isort]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should not be deleted too 😅

@devkapilbansal
Copy link
Member

If you are unsure how this will be done, then feel free to ask 😄

@devkapilbansal
Copy link
Member

@RiddhiAthreya are you working on this?

@isabelcosta
Copy link
Member

I will close this PR and unassign due to lack of response.
Thank you for your contribution @RiddhiAthreya so far :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Changes Requested Changes are required to be done by the PR author.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix: refactor HTTP error codes PUT /mentorship_relation/{request_id}/task/{task_id}/comment/{comment_id}
4 participants