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

Add a getter isModListOutdated #1633

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

VilppeRiskidev
Copy link
Collaborator

@VilppeRiskidev VilppeRiskidev self-assigned this Feb 11, 2025
Copy link
Collaborator

@anttimaki anttimaki left a comment

Choose a reason for hiding this comment

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

I think this PR was not ready for review.

@VilppeRiskidev VilppeRiskidev force-pushed the status-indicator-data branch 3 times, most recently from a151fd4 to 03a91ea Compare February 19, 2025 12:20

let conciseError = "Failed to load mod list";
if (isNetworkError(state.thunderstoreModListUpdateError)) {
conciseError = "Failed to download mod list due to network error"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could be "Failed to fully refresh the online mod list due to network error" to be consistent (if screen estate allows).

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Now that you mentioned this, it reminded me that I was also contemplating if the StatusIndicator's text should be a warning or an error (yellow vs. red text), but that's also definitely out of the scope of this PR. :D

Copy link
Collaborator

Choose a reason for hiding this comment

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

It's a partial failure so I'd say it's an error. Especially since some users seem to be confused about the status unless we're very in-your-face about it.

commit('setThunderstoreModListUpdateError',
new R2Error(
PARTIAL_UPDATE_ERROR,
`Only ${chunkCount - successes} out of ${chunkCount} chunks were updated successfully.`,
Copy link
Collaborator

Choose a reason for hiding this comment

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

  • Bug? Shouldn't this be Only ${successes} out of ${chunkCount}...
  • Nitpick but "chunks" might not mean so much to the users. "Parts" would be slightly better? Some other wording could also work.
  • If this ends in ., there will be two of them in the ImportProfileModal. Fix either here or there, but make sure all places where this is shown show 0..1 full stops.
  • ImportProfileModal and SettingsView currently show this error message. Is that intentional? Looks to me PARTIAL_UPDATE_ERROR is currently shown only if user opens the error modal in ModListUpdateBanner, and that might the more user-friendly part of the message. This too can be changed (if it's changed) either here in the error definition, or on the sites where the error is used.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

To comment on the last point: It was/is intentional, but can be changed if you think so.
I think it is nicer this way, because those two places it is prefixed with Error updating the mod list: .
In my opinion Error updating the mod list: Failed to fully refresh the online mod list. Some mod versions might be unavailable. would be a bit redundant, but there could be better wordings for this 🤔 I think it is kind of nice to show the numbers in most cases, but not necessarily on the StatusIndicator if that makes sense (if I was a user and it showed that it downloaded 99 out of 100 parts, I probably would just continue and be aware that something might be a bit broken and 1 success out of 100 would make me expect that it most likely is going to be broken.) That's my $0.02, feel free to ask for more changes.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Alright, let's go with as-is.

And I think you put more effort in writing the sentences about partial failure than some users will put into the whole thing. Seems to me that for them it's a binary thing, either it failed or it didn't, and the idea of "it didn't go quite as expected but you can try to continue" just doesn't register.

@VilppeRiskidev VilppeRiskidev force-pushed the status-indicator-data branch 2 times, most recently from a3bd45d to b91770a Compare February 24, 2025 16:29
Copy link
Collaborator

@anttimaki anttimaki left a comment

Choose a reason for hiding this comment

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

LGTM

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 this pull request may close these issues.

2 participants