-
Notifications
You must be signed in to change notification settings - Fork 467
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
Bundle resource needs some improvements #27782
Labels
Gardening Day
OKR : Quality Assurance
Owned by Bryan
QA : Approved
Release : 24.09.21
UVE // Java21
stale
Team : Falcon
Type : Defect
Comments
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
@bryanboza Is this issue still open? |
freddyDOTCMS
moved this from Gardening Day Backlog
to QA - In Progress
in dotCMS - Product Planning
Aug 30, 2024
freddyDOTCMS
moved this from QA - In Progress
to In Review
in dotCMS - Product Planning
Aug 30, 2024
freddyDOTCMS
added a commit
that referenced
this issue
Aug 30, 2024
freddyDOTCMS
moved this from QA - In Progress
to QA - Backlog
in dotCMS - Product Planning
Sep 3, 2024
Approved: Tested on dotcms-postman/src/main/resources/postman/Bundle_Resource.postman_collection.json, Postman, macOS 14.5 |
github-project-automation
bot
moved this from Done
to Internal QA
in dotCMS - Product Planning
Oct 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Gardening Day
OKR : Quality Assurance
Owned by Bryan
QA : Approved
Release : 24.09.21
UVE // Java21
stale
Team : Falcon
Type : Defect
Parent Issue
Related to #26201
Problem Statement
When you are deleting a bundle, we always are returning a 200 in the response with the follow message
"entity": "Removing bundles in a separated process, the result of the operation will be notified"
. Then does not matter if the bundle was deleted or not.At the response level, we are unable to know if we delete the bundle or not. We need to return a 404 error and the corresponding message in case the bundle does not exist.
Also, if you don't send body in that request, we are returning a 500 exception with a NPE in the log, we need to catch this exceptions and return the 400 (bad request) errror indicating the problem.
Here the log:
https://gist.github.com/bryanboza/21b5a4cf30950ebdee530b6117d38fbb
Steps to Reproduce
Acceptance Criteria
dotCMS Version
Tested on master // Docker // FF
Proposed Objective
Quality Assurance
Proposed Priority
Priority 2 - Important
The text was updated successfully, but these errors were encountered: