Skip to content

Refactor log4j2 logging#138

Closed
Kazzuk wants to merge 1 commit into
CloudburstMC:bleedingfrom
Kazzuk:log4j2
Closed

Refactor log4j2 logging#138
Kazzuk wants to merge 1 commit into
CloudburstMC:bleedingfrom
Kazzuk:log4j2

Conversation

@Kazzuk

@Kazzuk Kazzuk commented Dec 7, 2021

Copy link
Copy Markdown
Member

When using %-5level, it would return the priority level justified to a width of 5 characters, so for example if the level was INFO, you would be left with a trailing space after the level like so "INFO ". Using %level instead resolves this.

Before example:
image
After example:
image

@SupremeMortal

SupremeMortal commented Dec 7, 2021

Copy link
Copy Markdown
Member

This was done for consistency so the spacing for each log entry is exactly the same.

Current format

[FATAL] 1234567890
[ERROR] 1234567890
[WARN ] 1234567890
[INFO ] 1234567890
[DEBUG] 1234567890
[TRACE] 1234567890

Proposed format

[FATAL] 1234567890
[ERROR] 1234567890
[WARN] 1234567890
[INFO] 1234567890
[DEBUG] 1234567890
[TRACE] 1234567890

@Kazzuk Kazzuk closed this Dec 8, 2021
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