The data field is misleading as response can be anything - database, collection, role, message, etc. This data field may also be confused with data/datum entity.
So to make it less confusing,
Update the API response with a response field that would take all the values that data does
To ensure backward compatibility, the data field would NOT be removed immediately , but the response would have both the data and response fields returning the same data.
The data field would be phased out at some point in future [ #121 ]
Maybe add a (generic) notice field in response for deprecation warning. This field can be used for other purposes too. [ #122 ]
Currently the response has following field
The
data
field is misleading as response can be anything - database, collection, role, message, etc. Thisdata
field may also be confused with data/datum entity.So to make it less confusing,
response
field that would take all the values thatdata
doesdata
field would NOT be removed immediately , but the response would have both thedata
andresponse
fields returning the same data.data
field would be phased out at some point in future [ #121 ]notice
field in response for deprecation warning. This field can be used for other purposes too. [ #122 ]