Headless APIs missed value information when fails.

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.4.3.60 CE GA60, 7.4.13 DXP U60, Master
• Component/s: Headless Delivery API
• Labels:
  • 7.4-known-issues
  • 7.4.13-u60
  • fi-headless
  • liferay-ga28-ce-743-known-issues
  • liferay-ga29-ce-743-known-issues
  • liferay-ga30-ce-743-known-issues
  • liferay-ga31-ce-743-known-issues
  • liferay-ga32-ce-743-known-issues
  • liferay-ga33-ce-743-known-issues
  • liferay-ga34-ce-743-known-issues
  • liferay-ga35-ce-743-known-issues
  • liferay-ga36-ce-743-known-issues
  • liferay-ga37-ce-743-known-issues
  • liferay-ga38-ce-743-known-issues
  • liferay-ga39-ce-743-known-issues
  • liferay-ga40-ce-743-known-issues
  • liferay-ga41-ce-743-known-issues
  • liferay-ga42-ce-743-known-issues
  • liferay-ga44-ce-743-known-issues
  • liferay-ga45-ce-743-known-issues
  • liferay-ga46-ce-743-known-issues
  • liferay-ga47-ce-743-known-issues
  • liferay-ga48-ce-743-known-issues
  • liferay-ga49-ce-743-known-issues
  • liferay-ga50-ce-743-known-issues
  • liferay-ga51-ce-743-known-issues
  • liferay-ga52-ce-743-known-issues
  • liferay-ga53-ce-743-known-issues
  • liferay-ga54-ce-743-known-issues
  • liferay-ga55-ce-743-known-issues
  • liferay-ga56-ce-743-known-issues
  • liferay-ga57-ce-743-known-issues
  • liferay-ga58-ce-743-known-issues
• Story Points: 1
• Fix Priority: 3
• Sprint: Almost a Sprint, H01S02 - Wrath, H01S01 - Fossora, H01S03 - A Head Full of Dreams, H01S04 - Nuestro, H01S05 - Zyryab, H01S06 - First Impressions..., H01S07 - Name?
• Git Pull Request: https://github.com/liferay-headless/liferay-portal/pull/928
• Bug Type: Regression Bug

Due to the LPS-152965, value information given by the REST APIs was lost.

Steps to reproduce

• Create a blog with a POST request. For example:

 

{
  "articleBody": "2",
  "creator": {
    "familyName": "Test",
    "givenName": "Test",
    "id": 20129,
    "name": "Test Test",
    "profileURL": "/web/test"
  },
  "dateCreated": "2019-04-10T23:02:50Z",
  "dateModified": "2019-04-11T14:39:05Z",
  "datePublished": "2019-04-11T14:39:00Z",
  "encodingFormat": "text/html",
  "friendlyUrlPath": "12",
  "headline": "3",
  "id": 63706,
  "numberOfComments": 0,
  "siteId": 20123
}

• Send the POST request again

Expected result

 

The API response with a CONFLICT message and additional information to guide the developer to diagnose why it is failing.

{
  "status": "CONFLICT",
  "title": "Duplicate friendly URL"
}

Actual result

 

The API response just with CONFLICT

{
  "status": "CONFLICT"
}

Note that this is happening for all responses that are not 2XX under the headless APIs.

This makes the development harder as it increases the difficulty to diagnose why is the request failing.

This could break contracts with clients that are using the response to do some tasks, like showing a warning pop-up with the message.