fix(Attachment): Make get attachment endpoints consistent, allow to update project/component/release with attachment data #2917
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
=> These two issues make it difficult for us to create a common component for listing and editing attachments in the new front-end
This PR does:
How To Test?
1.Make get attachment endpoints response format consistent
Method: GET
Url:
- Project attachments: http://{ip}:8080/resource/api/projects/{project_id}/attachments
- Component attachments: http://{ip}:8080/resource/api/components/{component_id}/attachments
- Release attachments: http://{ip}:8080/resource/api/releases/{release_id}/attachments
Expected output:
2.Update project/component/response
Method: PATCH
Url:
- Update project : http://{ip}:8080/resource/api/projects/{project_id}/
- Update component: http://{ip}:8080/resource/api/components/{component_id}/attachments
- Update release: http://{ip}:8080/resource/api/releases/{release_id}/attachments
Body: