You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rather than teaching editors to open their browser's developer tools to retrieve a console log, we should include additional information in the message itself.
This could be accomplished in two ways:
Grab the response JSON and include the message attribute (low-effort, kiln-only change).
clay/amphora implements error handlers that return the following JSON when an exception is encountered (eg. during
model.save
):When Kiln encounters these errors it displays a generic
Error publishing article
in the "snack bar".This happens here while saving a component:
https://github.com/clay/clay-kiln/blob/master/lib/component-data/actions.js#L52-L71
And happens here on page publish:
https://github.com/clay/clay-kiln/blob/master/lib/drawers/publish-page.vue#L305-L314
Kiln has the context to display a more detailed message via
e.response
:clay-kiln/lib/core-data/api.js
Lines 114 to 116 in 8718789
Rather than teaching editors to open their browser's developer tools to retrieve a console log, we should include additional information in the message itself.
This could be accomplished in two ways:
message
attribute (low-effort, kiln-only change).uuid
in clay/amphora's error handler, log it in Amphora, display it in Kiln.The text was updated successfully, but these errors were encountered: