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

Hotfix/SUIT-16525-additional-log-options #368

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

Noorama
Copy link
Contributor

@Noorama Noorama commented May 20, 2021

No description provided.

@Noorama Noorama requested review from andriichumak and JeKachan May 20, 2021 14:37
@@ -56,7 +56,8 @@ const webSocketsFactory = (self) => {
content.type === 'console' &&
content.data[0] !== 'SUITESTIFY: domainMapping'
) {
const {args: data, method: level} = logger.getAppOutput(content.subtype, content.data);
const {args: data, method: level} = logger.getAppOutput(content.subtype, content.data)
|| {data: undefined, level: undefined};
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think u can use here empty object {}

@@ -76,7 +77,7 @@ const webSocketsFactory = (self) => {
const requestBody = logItem.request && logItem.request.requestBody;
const responseBody = logItem.response && logItem.response.responseBody;

if (config.logLevel === logLevels.debug) {
if (config.networkLogs === logLevels.debug || config.logLevel === logLevels.debug) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that specific log level should override general setting (have more weight). For example if logLevel defined debug, but networkLogs is not debugg (hidden for example) - network logs should not be displayed
@andriichumak what is preferable behavior?

Copy link
Contributor

@andriichumak andriichumak May 31, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree

@polomsky polomsky force-pushed the master branch 4 times, most recently from a7cd28b to ebd5e39 Compare March 6, 2024 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants