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

FE: provide empty state for plugin picker #88404

Closed
TimBroddin opened this issue Mar 12, 2024 · 3 comments · Fixed by #88617
Closed

FE: provide empty state for plugin picker #88404

TimBroddin opened this issue Mar 12, 2024 · 3 comments · Fixed by #88617
Assignees

Comments

@TimBroddin
Copy link
Contributor

In the create/edit schedule, let's provide an empty state for the plugin list view.

cc @JanaMW27

Context: #88376 (comment)

@JanaMW27
Copy link

hummm... is this in case the user doesn't have any plugin?
if that is the case they should not be able to access the feature no?

@TimBroddin
Copy link
Contributor Author

It's the case where the user doesn't have any plugin that's not managed by us. We currently show a banner in the add/edit view when this happens:

Image

It would be nice if we also show something inside the empty list view there.

@JanaMW27
Copy link

My take on this:

  • If no plugins can be included in an update schedule, the user shouldn't be able to access the feature.
  • If for some reason they still are able to access it, I would have an announcement on the empty schedules page saying: To set up schedules to manage your plugins, first you need to install plugins that are not managed by the plugin provider.
  • I would not have the Create a new schedule CTA and I would replace it with one that would take the user to the plugins page (Explore plugins)
  • I would not allow the user to access the New Schedule page
    Empty state

Is there a specific case scenario where they may still have access to a Schedule page even though no plugins are available?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants