Skip to content

Hard to control logging behavior for testing #65

@mitchlloyd

Description

@mitchlloyd

I'm using Jest for testing and I'd like to avoid the default logging from this plugin under test. I worked through all the logger, logger proxy, and logger publisher types to get a no-op logger into the Resource class. However, I was dismayed to find that there is one stray console.debug in the code.

I'm guessing this was added for expediency to avoid adding debug to the Logger interface. Could the Logger interface be updated to accommodate this debug level logging and then have this code call this.lambdaLogger.debug() instead of console directly?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions