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

Refactor ProfileInstallerProvider to use ImmutableProfile when enabling/disabling mods #1475

Merged
merged 7 commits into from
Oct 14, 2024

Conversation

anttimaki
Copy link
Collaborator

No description provided.

The method is not used anywhere, at least anymore.
The method isn't called from the outside and looks more like an
implementation detail for enableMod/disableMod methods.
applyModModeForSubdir creates FileTree objects internally and
applyModModeForState doesn't use FileTrees at all.
The location is always derived from the Profile object, which is passed
as an argument anyway. Furthermore, applyModModeForSubdir doesn't even
use the argument.
Ideally only ImmutableProfiles would be used, but settle for supporting
both Profiles and ImmutableProfiles for now to limit the scope of this
refactoring effort.
Now that the methods called by the actions which enable/disable mods
accept ImmutableProfiles as arguments, it makes sense for the actions
themselves to also use ImmutableProfiles.
Base automatically changed from immutable-profile-pt4-downloadprovider to develop October 14, 2024 11:58
@anttimaki anttimaki merged commit c761737 into develop Oct 14, 2024
5 checks passed
@anttimaki anttimaki deleted the immutable-profile-pt5-profileinstallprovider-mode branch October 14, 2024 11:59
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