Skip to content

Upgrade javascript logging #917

Open
@Rodhlann

Description

@Rodhlann

Is your idea related to a problem? Please describe.
Currently the Wildbook javascript code is using console.log or similar for logging purposes, and it may be worth investigating a more robust solution. These console usages are currently being flagged by eslint as warnings.

Describe the solution you'd like
Other logging libraries include Winston, Pino, etc.

Describe alternatives you've considered
There is not necessarily anything wrong with using console.log, though it is the rudimentary option. If we choose to stick with console.log in the future we should update the eslint config to disable the rule flagging existing logs.

Additional context
Update to logging suggested by @TanyaStere42 while investigating #867

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementnew or improvements on existing featuresproject_supportdevops, build changes, etc etcquestionopen investigation to define scope of issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions