- Issue created by @asherry
- Status changed to Fixed
over 1 year ago 3:30pm 28 March 2023 Automatically closed - issue fixed for 2 weeks with no activity.
The response object functionality was originally intended to extend one class with simple ->get[property name] and set[property name]. These methods would then be converted into properties in the api response for GET, and/or saved when a POST was sent.
It then ballooned into a number of controller methods needed to load multiple, save multiple, an entity wrapper class, traits to handle regular entity save functionality, access handlers, exceptions, warning messages, etc.
When it was created originally it was already re-inventing the wheel. The rest module has had all these capabilities, though required a little bit more overhead in initial development for custom api responses.
Remove all response object functionality. The usage for this module is pretty low right now, and the usage for this particular functionality is even lower. The controller functionality never made it to the contrib version.
Fixed
2.0
Code
Automatically closed - issue fixed for 2 weeks with no activity.