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

fix: disable "Update All" button when an invalid repo is detected #1500

Merged
merged 4 commits into from
Oct 10, 2024

Conversation

matmen
Copy link
Member

@matmen matmen commented Oct 1, 2024

The "Update All" action updates all components sequentially and fails if there's an invalid repository up next. When the first updatable repo in the list is an invalid one, this would just refresh fluidd without actually doing anything, resulting in poor UX and confused users (me 🤣). Not sure if this also affects dirty repos, I haven't had time to test that yet.

Not sure this approach is better, because it just disables the update button without showing a reason for it. Maybe the button should have a tooltip showing the reason for it being disabled too?

out.mp4

@matmen matmen added the GH - Bug Something isn't working label Oct 1, 2024
@matmen matmen added this to the 1.30.5 milestone Oct 1, 2024
@matmen matmen requested a review from pedrolamas October 1, 2024 18:59
@matmen matmen marked this pull request as draft October 1, 2024 21:05
Signed-off-by: Mathis Mensing <[email protected]>
@matmen matmen marked this pull request as ready for review October 2, 2024 20:07
Copy link
Member

@pedrolamas pedrolamas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@matmen matmen merged commit a2cc361 into fluidd-core:develop Oct 10, 2024
4 checks passed
@matmen matmen deleted the fix/no-full-update-dirty-repo branch October 10, 2024 11:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GH - Bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants