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
In #658 we re-introduced the notification for a single-resource editor which tells the user that the resource was successfully created.
We're still missing this for the multi-resource editor.
Result:
Nothing happens. There's no notification that tells you that the resource were successfully created. You only get a notification if something goes wrong and resources could not get created
Expected result:
I want to be informed that the resources were created on the cluster. Of course I'd also like to know of errors. So the notification should inform of both: success and errors. It's currently not evident how to inform properly as notifications currently only have single line and a single icon: they either inform of success (for the single resource editor) or errors (for both, the single resource editor or the multi resource editor)
The text was updated successfully, but these errors were encountered:
related to #658
In #658 we re-introduced the notification for a single-resource editor which tells the user that the resource was successfully created.
We're still missing this for the multi-resource editor.
Steps:
Result:
Nothing happens. There's no notification that tells you that the resource were successfully created. You only get a notification if something goes wrong and resources could not get created
Expected result:
I want to be informed that the resources were created on the cluster. Of course I'd also like to know of errors. So the notification should inform of both: success and errors. It's currently not evident how to inform properly as notifications currently only have single line and a single icon: they either inform of success (for the single resource editor) or errors (for both, the single resource editor or the multi resource editor)
The text was updated successfully, but these errors were encountered: