Desired Behavior
Present errors on the :base of an object to admin users. Errors should be presented whenever objects are being created or updated and they fail due to object-level validation errors.
(Optional) Current Behavior
Currently, no error is presented to the user. A 422 turbo request occurs in the background, but it does not surface what went wrong.
(Optional) Additional notes
- We could categorize this as a bug, but I think the kind of work that needs to be done is more feature-like.
- Ideally, every
@resource record with object-level validation errors on it can be treated the same way. But we should implement it in such a way that developers can redefine functionality per resource. (Just look at how the existing ResourcesController and resource base components work.)
- I think that we should use the existing
flash[:alert] functionality that solidus_admin provides to surface these errors.
Desired Behavior
Present errors on the
:baseof an object to admin users. Errors should be presented whenever objects are being created or updated and they fail due to object-level validation errors.(Optional) Current Behavior
Currently, no error is presented to the user. A 422 turbo request occurs in the background, but it does not surface what went wrong.
(Optional) Additional notes
@resourcerecord with object-level validation errors on it can be treated the same way. But we should implement it in such a way that developers can redefine functionality per resource. (Just look at how the existingResourcesControllerand resource base components work.)flash[:alert]functionality thatsolidus_adminprovides to surface these errors.