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?

Commencez par la discussion dans #129 et par l’abstraction Operation existante afin de comprendre comment les requêtes CRUD sont actuellement traitées. Définissez ce qu’un point d’extension pour des opérations spécifiques aux ressources devrait prendre en charge, notamment la création de ressources associées tout en conservant une API externe basée sur CRUD et conforme à JSON:API ; la finalisation doit inclure une approche service-object maintenable ainsi que des éléments démontrant que le comportement est testable.