backend:Implement Listing Issues Endpoints (LabelLab 13)

[M-A-D-A-R-A]

Description

Implement Listing Issues Endpoints

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

URL and Responses:-

• Fetch all Issue in a project :- URL:- BASE_URL +/api/v1/issue/get/<int:project_id> Example URL: URL:- BASE_URL +/api/v1/issue/get/1
  • Fetch Issue by Catergory:- URL:- BASE_URL +/api/v1/issue/<int:project_id>/category/<string:category> Example URL: URL:- BASE_URL +/api/v1/issue/1/category/images
  • Update Issue by team ID: -URL:- BASE_URL +/api/v1/issue/<int:project_id>/team/<int:team_id> Example URL: URL:- BASE_URL +/api/v1/issue/1/team/1
  • Fetch issue by Entity Type and ID:- URL:- BASE_URL +/api/v1/issue/<int:project_id>/entity/<string:entity_type>/<int:entity_id> Example URL: URL:- BASE_URL +/api/v1/issue/1/entity/label/1

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules

[amlannandy]

@M-A-D-A-R-A There are merge conflicts. Sync your fork and local with the organization repo. Then resolve the merge conflicts and push the changes.

[M-A-D-A-R-A]

Yeah Sure

[amlannandy]

Yeah Sure

There are still some conflicts. Did you sync your branch with upstream ?

[M-A-D-A-R-A]

Yeah Sure

There are still some conflicts. Did you sync your branch with upstream ?

Yeah I did Fetch the upstream, I tried merging master again in this branch there's no merge conflict.

Should I close this PR and make another one?

[amlannandy]

@M-A-D-A-R-A No that should not be necessary. Can you go through all the files that you've made changes to in this PR and make sure there are no leftover conflicts in any of them? You've synced your fork with the org repo but you perhaps missed resolving the conflict.

[amlannandy]

Try out this from your current branch.

git fetch upstream

git rebase upstream/master

Then push the changes. Force push if necessary.

[M-A-D-A-R-A]

Try out this from your current branch.

git fetch upstream

git rebase upstream/master

Then push the changes. Force push if necessary.

I tried these and made the necessary changes to each commit idk why it's saying merge conflicts.

[amlannandy]

Try out this from your current branch. git fetch upstream git rebase upstream/master Then push the changes. Force push if necessary.

I tried these and made the necessary changes to each commit idk why it's saying merge conflicts.

Yeah this is weird. Let me check it out in the evening. Otherwise I'll merge it locally.