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

DownloadModModal refactoring #1289

Merged
merged 3 commits into from
Apr 15, 2024
Merged

Conversation

anttimaki
Copy link
Collaborator

Did the changes as preparation for showing installation progress along the download progress. That turned to be a more complex issue than I first thought, so it's on a backburner for now. But I think the changes here can be merged anyways.

The exact same method couldn't be for .downloadSpecific() since it has
a bit different functionality and passing a specific Profile would
require changes to DownloadProvider interfaces.
None of the methods in DownloadProviders expect completedCallback
argument to return an error, or any value for that matter.
.downloadSpecific() which returns a promise should reject the error so
the caller in Manager.vue can handle it with promise's catch.

The methods called by UI components in DownloadModModule that use
the .downloadCompletedCallback() helper should open the error modal
themselves.
Changing from any type to a proper type reveals that the object can be
null in couple of places - non-null assertions are used for these to
avoid having to deal with these right now.
@anttimaki anttimaki force-pushed the downloadmodmodal-refactoring branch from 8c01d57 to 52ed2bc Compare April 15, 2024 06:49
@anttimaki anttimaki merged commit dd003ba into develop Apr 15, 2024
7 checks passed
@anttimaki anttimaki deleted the downloadmodmodal-refactoring branch April 15, 2024 06:58
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.

1 participant