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: UI Enhancements #111

Closed
emouawad opened this issue Jan 28, 2025 · 8 comments
Closed

Feature Request: UI Enhancements #111

emouawad opened this issue Jan 28, 2025 · 8 comments
Labels
enhancement New feature or request

Comments

@emouawad
Copy link

User stories

  • As a user i need a snappier UI with better "refresh"

Feature description

These are mere suggestions, please don't get me wrong love the project ❤; I've been waiting for something like this for some time, tried other solutions but they all needed so much manual configuration.

If i may suggest:

  • "New data available" is annoying - even if dismissed pops up again.
  • Manual refresh is so 2000. Currently reloads the whole UI instead of partial updates to only what changed.
  • Prefer an autorefresh view where the UI renders the changes only.
  • Use polling to communicate to the backend or websockets to notify of the backend updates to be reflected in the UI.
  • After filter is applied: The back button doesn't return to the filtered results instead to home but browser history works.
  • Pages are misleading Page 2 button is /?page=1 in the url
@emouawad emouawad added the enhancement New feature or request label Jan 28, 2025
@AlexGustafsson
Copy link
Owner

Thanks for the report. I have a few questions to understand your use case.

  • Do you often use Cupdate after the initial update / scan?
  • Do you keep it open as a dashboard window?
  • Are you using the default config for things like the worker interval?

By default data is checked so seldom that I thought it would be rare to actually time an update when being on the web app. Hence, the refresh was mostly a development thing for testing the per-image refresh, which in turn was mostly a development feature. So I've never bothered to make the refresh that good in the first place.

@emouawad
Copy link
Author

Well yes - I would like to be able to check the dashboard a lot since it includes a lot of valuable information besides version and vulnerability like the github repo, readme, dockerhub link, release changelog, kubernetes namespace - lots of necessary information for a Kubernetes admin to prioritize maintenance and upgrades.
I could see myself checking it multiple times a day regularly.
The data gathered is excellent - with a good UI it's a killer for devops.

Btw not sure if it's a bug or what - the moment i dismiss the popup "New data available" it comes back again immediately. (Keeping the browser page open in the background)

Thanks.

@AlexGustafsson
Copy link
Owner

AlexGustafsson commented Jan 28, 2025

Thanks! I've been working on a few improvements addressing some of your concerns. I'll let you know when you can try it out.

Btw not sure if it's a bug or what - the moment i dismiss the popup "New data available" it comes back again immediately. (Keeping the browser page open in the background)

That's somewhat of a limitation with the current change detection. Essentially there's not any nice way of diffing what's changed in sqlite when some part of an image is updated (such as its README). Therefore, an event is triggered whenever anything looks like it's been changed. As that could be the README, or basic information like the version, it's possible that you'll get a couple of events immediately after one another. Cupdate also processes images in batches, so it's entirely likely that each image in the batch would fire an event almost simultaneously. I'm looking to address that in the near future.

@AlexGustafsson
Copy link
Owner

I've merged the following fixes to main, should be out on latest:

  • Keep query when going back from image page
  • Update data without refresh

I'm still showing the toast, but the wording is updated and instead of refreshing the page it just reloads the content automatically. I'll probably keep the update manual for now as I think it would be annoying if content on the page moves around / changes all of the sudden.

There's one known limitation in that once you've triggered a manual update, you won't be able to trigger it again unless you leave the page.

@emouawad
Copy link
Author

Great thanks! looking forward to testing it tonight.

@AlexGustafsson
Copy link
Owner

In the latest version, page indexes now start at 1. I think that means all your concerns but one have been adressed.

"New data available" is annoying - even if dismissed pops up again.

As I've mentioned, that's something I hope to improve in the future.

@emouawad
Copy link
Author

Yes i just tried it.
Thanks - much appreciated ❤

@emouawad
Copy link
Author

@AlexGustafsson I believe with the latest update, the UI is now much better. Thanks! Closing.

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

No branches or pull requests

2 participants