Skip to content

refactor(logging): aligned error messages with reporting criticality#1317

Merged
JosefBredereck merged 3 commits intopattern-lab:devfrom
mfranzke:refactor-error-loggings-criticality
May 17, 2021
Merged

refactor(logging): aligned error messages with reporting criticality#1317
JosefBredereck merged 3 commits intopattern-lab:devfrom
mfranzke:refactor-error-loggings-criticality

Conversation

@mfranzke
Copy link
Contributor

Closes #1315

Summary of changes:

If we call it an error in the logging message, we should even also mark it as an error instead of an info or a warning. This is as well related to console output depending on the log level setting within the configuration.

The changes on lines 67 and 75 within the file packages/plugin-tab/src/tab-loader.js are unrelated to the contents of this change request, but most likely triggered by automatic prettifying through prettier/pretty-quick by husky git commits.

If we call it an error in the message, we should even also mark it as an error instead of an info or a warning
@JosefBredereck JosefBredereck merged commit 0945d64 into pattern-lab:dev May 17, 2021
@mfranzke mfranzke deleted the refactor-error-loggings-criticality branch May 17, 2021 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error parsing pseudo-pattern emits only a warning

2 participants

Comments