Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JS logging level management #1773

Open
joelit opened this issue Mar 13, 2025 · 0 comments
Open

JS logging level management #1773

joelit opened this issue Mar 13, 2025 · 0 comments
Milestone

Comments

@joelit
Copy link
Contributor

joelit commented Mar 13, 2025

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.

@github-project-automation github-project-automation bot moved this to Proposed Skosmos 3.0 issues (to do) in Skosmos 3.0 Backlog Mar 13, 2025
@joelit joelit modified the milestone: 3.0 Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Proposed Skosmos 3.0 issues (to do)
Development

No branches or pull requests

1 participant