satisfactorymodding / satisfactorymodding/ficsit-cli
Graph visualization on mod resolution errors
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 69
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
Users can be confused by resolution error messages
Describe the solution you'd like
Show a graph together with the error message
Describe alternatives you've considered
No response
Additional context
┌──────┐
│ Root │
└─┬──┬─┘
┌─────┘ └─────┐
┌──────────────┴─┐ ┌─┴──────────────┐
│ Power Extras │ │ Area Actions │
│ (gPowerExtras) │ │ (AreaActions) │
│ * │ │ 1.6.5 │
└──────────────┬─┘ └─┬──────────────┘
│ │
┌──────────────┴─┐ ┌─┴──────────────┐
│ SML │ │ SML │
│ (SML) ├────┤├────┤ (SML) │
│ 2.2.1 │ │ ^3.0.0 │
└────────────────┘ └────────────────┘
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the CLI's mod-resolution error handling and how those errors are rendered. Define the dependency graph cases represented by the issue's example, then implement graph output alongside the error message; done means resolution failures present an understandable graph without losing the existing error details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100