Skip to content

Use more appropriate/granular LogLevel with LoggerMessageAttribute #3

@david-acker

Description

@david-acker

Background

LogLevel.Information is currently used for all (or almost all) of the LoggerMessageAttribute-based logging.

Solution

These individual logging methods should be reviewed and given a more appropriate LogLevel based on their specific context or importance. For example, logs related to duplicate dependencies being found while mapping should like be LogLevel.Debug, and hidden by default, as there's really no purpose in showing this information to the end user in for common, expected events like these.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions