You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that when an error thrown from the client, the error response always contains the statusCode, while if the query successfully executed, I have to pass the meta property to read the statusCode. I see that as unconsistancy in the design.
I'm proposing to return always the statusCode when the query successfully executed. It's light and important value and it will not affect the transfer response time.
Currently I'm forced to let the .then return an object contains the statusCode hard coded.
Motivation
In my company we are upgrading from ES7 to ES8, and we saw the breaking change where the meta property should be passed in order to read the response values such as statusCode.
The text was updated successfully, but these errors were encountered:
馃殌 Feature Proposal
I noticed that when an error thrown from the client, the error response always contains the statusCode, while if the query successfully executed, I have to pass the meta property to read the statusCode. I see that as unconsistancy in the design.
I'm proposing to return always the statusCode when the query successfully executed. It's light and important value and it will not affect the transfer response time.
Currently I'm forced to let the .then return an object contains the statusCode hard coded.
Motivation
In my company we are upgrading from ES7 to ES8, and we saw the breaking change where the meta property should be passed in order to read the response values such as statusCode.
The text was updated successfully, but these errors were encountered: