Skip to content

fix: declare loggers with the enclosing class, not another/super class#1387

Merged
joaodinissf merged 1 commit into
dsldevkit:masterfrom
joaodinissf:fix/wrong-logger-class-literals
Jun 1, 2026
Merged

fix: declare loggers with the enclosing class, not another/super class#1387
joaodinissf merged 1 commit into
dsldevkit:masterfrom
joaodinissf:fix/wrong-logger-class-literals

Conversation

@joaodinissf

Copy link
Copy Markdown
Collaborator

Three LogManager.getLogger(...) declarations used the wrong class literal, so their log records appear under an unrelated category:

File Was Now
EObjectDescriptions NameFunctions.class (unrelated class) EObjectDescriptions.class
DefaultCheckQuickfixProvider DefaultQuickfixProvider.class (superclass) DefaultCheckQuickfixProvider.class
CustomClassAwareEcoreGenerator EcoreGenerator.class (superclass) CustomClassAwareEcoreGenerator.class

Each declares its own LOGGER field, so the category should be the enclosing class. Found by a repo-wide inconsistency sweep.

🤖 Generated with Claude Code

Three loggers were created for the wrong category, so their records show up
under an unrelated class:
- EObjectDescriptions used getLogger(NameFunctions.class) (unrelated class)
- DefaultCheckQuickfixProvider used its superclass DefaultQuickfixProvider
- CustomClassAwareEcoreGenerator used its superclass EcoreGenerator

Use the enclosing class literal in each, per the LogManager.getLogger
convention.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@joaodinissf joaodinissf marked this pull request as ready for review May 30, 2026 16:00
@joaodinissf joaodinissf enabled auto-merge (rebase) May 30, 2026 16:35
@joaodinissf joaodinissf merged commit 5977f10 into dsldevkit:master Jun 1, 2026
4 checks passed
@joaodinissf joaodinissf deleted the fix/wrong-logger-class-literals branch June 1, 2026 07:38
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