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
Currently we have no UX/UI hints that a Job's body is invalid.
At the moment, the only invalid state that exists is when the body for the code editor is empty.
In future, we will have another story expanding this for other error states.
Lets not change the Ecto model validation messages: i.e. "body can't be blank".
But rather use the .errors struct and it's metadata to determine if the validation failure for body is from a validate_required etc.
The text was updated successfully, but these errors were encountered:
Add an error label next to the "Save" button in the editor modal when the editor is empty
This is for immediate feedback when you try and save your changes.
Add an error label next to the editor button in the job settings modal
This is for when you've gone out of the editor modal while still in an invalid state. Otherwise you might run into the situation where we indicate the presence of an invalid node (Show that a node is invalid #956) but you can't see what's actually invalid.
Currently we have no UX/UI hints that a Job's body is invalid.
At the moment, the only invalid state that exists is when the body for the code editor is empty.
In future, we will have another story expanding this for other error states.
Technical Notes
Unlike #956 this button exists in LiveView.
Lets not change the Ecto model validation messages: i.e. "body can't be blank".
But rather use the
.errors
struct and it's metadata to determine if the validation failure forbody
is from avalidate_required
etc.The text was updated successfully, but these errors were encountered: