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?

Inizia dalla discussione in #129 e dall’astrazione Operation esistente per comprendere come vengono gestite attualmente le richieste CRUD. Definisci cosa dovrebbe supportare un punto di estensione per le operazioni specifiche delle risorse, inclusa la creazione di risorse correlate, mantenendo al contempo l’API esterna basata su CRUD e conforme a JSON:API; il completamento dovrebbe includere un approccio service-object manutenibile e prove che il comportamento sia verificabile tramite test.