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

Mismatch file detection - iteration 2 #261

Open
meza opened this issue Feb 11, 2023 · 0 comments
Open

Mismatch file detection - iteration 2 #261

meza opened this issue Feb 11, 2023 · 0 comments
Labels
enhancement New feature or request planned This feature is planned to be developed

Comments

@meza
Copy link
Owner

meza commented Feb 11, 2023

There has been a temporary, iteration 1 version of this done in #233 but it's far from elegant.

Here's what needs to be done:

Every operation should verify that the lockfile only contains mods that are in the config.
Every operation should evaluate the files in the mods directory.

A file could be:

  • fully managed (appears in the config and the lockfile)
  • partially managed (appears in the config but NOT in the lockfile)
  • mismatched (appears in the config but the lockfile hash differs)
  • not managed (does not appear in the config or the lockfile)

The list of mod files in the mod directory will have to come as a list with either one of the statuses above and every operation should deal with them accordingly.

The INSTALL (and consequently the UPDATE) action should remove the file in error and use whatever is in the lockfile
The SCAN action should ask what to do
The LIST action should show these statuses too

With these changes, the SCAN functionality might get redundant or change in responsibility.

Originally posted by @meza in #233 (comment)

@meza meza added enhancement New feature or request planned This feature is planned to be developed labels Feb 11, 2023
@meza meza modified the milestone: 1.3.0 Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request planned This feature is planned to be developed
Projects
None yet
Development

No branches or pull requests

1 participant