[explore]chart missing dataset open error msg

[junlincc]

We want to make sure PRs that introduce UI changes from the community are always welcome without follow strict guideline when they are first created. Design support will follow after these PRs are open if we can't provide Product and Design support upfront. tagging design-sys-revisit to track and prevent system level design debt.

#12705

'@junlincc @mihir174 feel free to create another issue to track followups if you want to update the design or copy.'
'A possible followup would be to add "Delete chart" shortcut CTA to make it easier for chart owners to delete outdated charts.'

[junlincc]

@ktmud @mistercrunch FYI ^ above is a temporary solution for balancing velocity and design quality, and for keeping OSS product development process transparent and open in the community.

[mistercrunch]

@junlincc I like it.

Seems like the "CHANGE DATASET" button should be styled in orange/warning too to avoid blue-on-orange

[geido]

We are cleaning up the labels and trying to reduce the amount. I believe need:design-review is appropriate and generic enough to catch PRs and issues that require design consideration, while design:proposal is appropriate for design proposals from the community.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

[rusackas]

Much of this flow has been redesigned/re-engineered since this was open, and I believe the issue has been largely addressed. If there are nuances to the new flow that are perceived as bugs, or need hashing out as a design/feature discussion, let's open fresh Issues and Github Discussions accordingly. Thank you!