Fallout-build / Fallout-build/Fallout

Print full level names in console output instead of three-letter abbreviations

Open Beginner friendly
#570 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C#
Stars
154
Forks
19
Avg merge
1d 22h
Merged PRs (30d)
15

Description

### Problem
Console output labels every line with a three-letter level abbreviation ([src/Fallout.Build/Logging.cs:27-28](https://github.com/Fallout-build/Fallout/blob/main/src/Fallout.Build/Logging.cs#L27-L28)):

```
22:49:44 [DBG] git version 2.50.1 (Apple Git-155)
22:49:44 [INF] > /usr/bin/git --version
22:49:44 [WRN] a warning line
22:49:44 [ERR] an error line
```

`VRB`, `DBG`, `INF`, `WRN`, `ERR` and `FTL` are not self-explaining. A reader has to learn the codes, and `VRB` versus `DBG` is not obvious even once you have.

The abbreviations exist to keep the level column a fixed width so messages line up. That is worth having, but it is not worth paying for with abbreviations — alignment should come from the layout, not from truncating the words.

### Outcome
Console lines are labelled with the full level name.

```
22:49:44 [Debug] git version 2.50.1 (Apple Git-155)
22:49:44 [Information] > /usr/bin/git --version
22:49:44 [Warning] a warning line
22:49:44 [Error] an error line
```

### Acceptance criteria
- [ ] Console output shows `[Debug]`, `[Information]`, `[Warning]`, `[Error]`, `[Verbose]`, `[Fatal]`
- [ ] The errors-and-warnings summary block uses the same names
- [ ] Level colouring is unaffected
- [ ] Specs cover every level for both console templates

### Notes
Message alignment is deliberately not preserved here. Column layout is #391s job, where Spectre owns the frame and can indent or lay out a real column instead. Scope is the console templates only: the `build.log` file templates keep their compact single-letter column format.

Contributor guide

Open the contributing guide

Research direction

Start at src/Fallout.Build/Logging.cs:27-28 and locate the console templates plus the errors-and-warnings summary. Run the existing logging specs to identify both console-template cases. Done means every level uses its full name in both outputs, level colouring remains unchanged, and specs cover Verbose, Debug, Information, Warning, Error, and Fatal.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
cli
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.