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.

Sign up for GitHub

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

Jump to bottom

BrowserLogger does not map to Console API functions (error(), warn(), debug(), ...) #18

Open
ansiwen opened this issue Jul 15, 2020 · 0 comments
Open

BrowserLogger does not map to Console API functions (error(), warn(), debug(), ...) #18

ansiwen opened this issue Jul 15, 2020 · 0 comments

Comments

@ansiwen
Copy link

ansiwen commented Jul 15, 2020

The Console API includes functions for logging on different severity levels, like error(), warn(), info() etc. Using these functions would allow filtering in the browser console.
ansiwen added a commit to ansiwen/bs-log that referenced this issue Jul 15, 2020
@ansiwen
BrowserLogger: Use Console API functions for logs without data
66c8625 
The Console API of browsers offer several functions for logs of
different severity levels, like error, warn, info, debug. This change
uses these functions instead of groupCollapsed for simple logs without data.
This allows to filter for logs in the browser console and allows the
browser to automatically group repeating logs.

Fixes: shakacode#17, shakacode#18

Signed-off-by: Sven Anderson <sven@anderson.de>
@ansiwen ansiwen mentioned this issue Jul 15, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ansiwen