Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Add empty state #4610

Closed
ndabAP opened this issue Jul 14, 2018 · 11 comments · Fixed by #19247
Closed

[Feature Request] Add empty state #4610

ndabAP opened this issue Jul 14, 2018 · 11 comments · Fixed by #19247
Assignees
Labels
C: New Component This issue would need a new component to be developed. C: VEmptyState T: feature A new feature

Comments

@ndabAP
Copy link

ndabAP commented Jul 14, 2018

What problem does this feature solve?

It's part of the Material Design guidelines and provides user friendliness.

What is your proposed solution?

An empty state component to be inserted everywhere, like here.

@ndabAP ndabAP changed the title Add empty state [Feature Request] Add empty state Jul 14, 2018
@ndabAP
Copy link
Author

ndabAP commented Jul 17, 2018

what do you mean by empty state

A call to action to increase the user engagement. I think it's pretty clear.

The answer to that question is completely related to the project and the use cases

Most real world examples from Google consist of an image and a text. The table component already supports the empty state with the property no-data-text. My use case would be the first example at the Material Design guidelines. It's used at Google Inbox.

Would you have an empty state for a button?

I don't see any purpose here. There is no real world example as I know.

@peterthomassen
Copy link

I agree. I would think that most data tables need an empty state. This is already supported through no-data-text, but no image can be set. However, the Material Guidelines say:

The most basic empty state consists of a non-interactive image and a text tagline.

It would be nice if that "most basic" interpretation would be supported. A neutral image default might not hurt, either.

(From the quote, you can also see that buttons usually are not in scope for this.)

@KaelWD
Copy link
Member

KaelWD commented Jul 30, 2018

but no image can be set

There is a no-data slot too.

@peterthomassen
Copy link

aha! In that case, I concur and don't think anything needs to be done. (I missed in the docs that the table with the props also has a "slots" tab. Still new -- sorry.)

@06b
Copy link
Contributor

06b commented Aug 27, 2018

Depending on the application I can see some cases where the no-data slot could work for an empty state, but I think there is still some validity to adding an empty state slot in addition to having a no data state.

For example - a no-data slot that states "No Data - Please adjust your filter criteria and try again." might be a correct statement to give a user however that message might not be the best first impression to give a user.

@peterthomassen
Copy link

How about a v-if inside the no-data slot, to distinguish these two cases?

@06b
Copy link
Contributor

06b commented Aug 27, 2018

The funny thing is I'm actually doing a v-if already in the no-data slot related to #4965 in the project I'm working on and I happen to be hiding the data-table for my empty state, but every project is different.

Ultimately "It Depends™" :)

@johnleider johnleider added this to the v2.0.0 milestone Sep 15, 2018
@johnleider johnleider added the T: feature A new feature label Sep 15, 2018
@johnleider johnleider self-assigned this Sep 15, 2018
@MajesticPotatoe MajesticPotatoe added the C: New Component This issue would need a new component to be developed. label Apr 10, 2019
@johnleider
Copy link
Member

Since this component is very basic, I have no issues with implementing it. However, it's not going to make v2.0 release.

@johnleider johnleider modified the milestones: v2.0.0, v2.x.x Jun 10, 2019
@johnleider johnleider modified the milestones: v2.x.x, v3.0.0 Jan 15, 2020
@johnleider
Copy link
Member

To give everyone an update. @DRoet is going to champion the development of this component. It's being moved off of a minor release in 2.x due to the upcoming release of Vue 3 and the preparations that are being taken to prepare for it.

@johnleider johnleider assigned DRoet and unassigned johnleider Jan 15, 2020
@mertyertugrul
Copy link

I am looking forward to this.

@TibebeJS
Copy link

any update/progress on this component please

@KaelWD KaelWD removed this from the v3.0.0 milestone Dec 23, 2021
@johnleider johnleider modified the milestones: v3.x.x, v3.6.0 (Nebula) Jan 22, 2024
johnleider added a commit that referenced this issue Feb 20, 2024
@johnleider johnleider self-assigned this Feb 20, 2024
johnleider added a commit that referenced this issue Feb 25, 2024
johnleider added a commit that referenced this issue Feb 25, 2024
johnleider added a commit that referenced this issue Feb 28, 2024
VIXI0 pushed a commit to VIXI0/vuetify that referenced this issue Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: New Component This issue would need a new component to be developed. C: VEmptyState T: feature A new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants