EverestAPI/Everest

Improvements to the Dependency Installer

Open

#331 opened on Jun 27, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (104 forks)auto 404
discussionhelp wanted

Repository metrics

Stars
 (503 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently when downloading dependencies, if a dependency is installed but blacklisted it will be re-enabled. However, there is no check to make sure that the mod is the right version. Blacklisted mods should be automatically updated if necessary when they are enabled by the dependency installer.

Dependencies should also be installed recursively if possible, to avoid multiple cycles of installing -> restarting -> installing.

Contributor guide

Research direction
Examine the dependency installer code to understand how blacklisted mods are handled and how dependencies are resolved. Focus on implementing version checks for blacklisted mods and adding recursive dependency installation to avoid multiple install restart cycles.
Tech stack
csharp
Domain
backendtooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65