Having JSONAPI::Rails::ActiveModelError inherit from JSONAPI::Serializable::Error makes it more intuitive to extend it in application-specific ways. For example, defining status and code properties using the mechanisms provided in the base class.
Thanks for this. The end goal is, indeed, to provide a way to customize this, but at the moment I'm not sure what the best interface is, so I'll keep this open until we figure it out.
Having
JSONAPI::Rails::ActiveModelError
inherit fromJSONAPI::Serializable::Error
makes it more intuitive to extend it in application-specific ways. For example, definingstatus
andcode
properties using the mechanisms provided in the base class.