Skip to content

JS logging level management #1773

@joelit

Description

@joelit

Description of the enhancement

We are using console.log here and there, but it's not defined when and how much we should log. Especially it is unclear whether some lines of logging are left there unintentionally as part of development and debugging.

Who are the users that would benefit from the enhancement and how?

Logging is useful for development and bug hunting, especially if it's kept to a relevant amount of information.

What new functionalities would the enhancement make possible?

If we moved to console.debug , console.error , console.info and console.warn , we could fine tune logging and also set up more consistent logging practises. Even better id set up a skosmos-logger, where we can filter the logging visibility (e.g. skosmos-logger.debug) to console by setting a logging level in config.

Why is the enhancement important?

It's common practise.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Proposed Skosmos 3.x issues

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions