Custom Operations

As per discussed in #129, I would like to do other tasks within a CRUD operation.

For my specific use case, I would like to create related resources upon creating a parent resource. The API is still strictly CRUD and compliant with JSONAPI, but under the hood I would like to have business logic that lives on the server side rather than the client. I found that decoupling this sort of code into service objects have been great for testing and maintainability, and it looks like Operation is exactly that.

Perhaps we can refactor it such that users of this gem can write their own operations for specific resources?

Comienza con la discusión en #129 y la abstracción Operation existente para entender cómo se gestionan actualmente las solicitudes CRUD. Define qué tendría que admitir un punto de extensión para operaciones específicas de recursos, incluida la creación de recursos relacionados, manteniendo al mismo tiempo la API externa basada en CRUD y conforme con JSON:API; la finalización debe incluir un enfoque de service-object mantenible y evidencia de que el comportamiento se puede probar.