sqlfilter inconsistent response
Description
PRDE - Internal Support default text according to the team DoR (Definition of Ready)
1 - DESCRIBE THE ISSUE YOU'RE HAVING:
The API request is failing but the BE is sending a status code of 200 from the backend instead 400.
Also, the content type is set to "application/json," but the actual response received is a string instead of a JSON object.
Return the reason of this error is also valid.
I am sending a POST to '/api/v2/queries/sqlfilter' and sending an invalid query.
2 - DESCRIBE ALTERNATIVES YOU CONSIDERED:
3 - ADD AS MUCH CONTEXT AS POSSIBLE (LINKS, SLACK CONVERSATIONS, SCREENSHOTS, ETC):
Activity
Show:
Details
Priority
HighestAssignee
Lucas Noetzold
Reporter
MARCOS STUMPF
Labels
CAROL_BACKLOG_REVIEWDEMOPLANNEDREADYREVIEWED
Due Date
25 March 2024
Fix versions
CAPL_4.01
Components
ORGANIZATION/TENANT | SWAGGER/APIS
Created
31 January 2024, 15:53
Updated
19 April 2024, 10:16
More fields
Created: 31 January 2024, 19:53
Updated:
19 April 2024, 15:16
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by olivandre,douglascoimbra.
Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).
feat: return error with syntax message on sqlfilter endpoint
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
validado pelo time de QA, pendente apenas do code review.
Sent by Slack - plataforma-carol-internal - Moisés
Bad request
Status 200
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
feat: return error with syntax message on sqlfilter endpoint
@MARCOS STUMPF ,
@Pedro Buzzi ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-03-25. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-03-25
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.