Skip to content

logger level #9

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

Merged
merged 1 commit into from
Jul 10, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/shared/topcoder/challenges.service.ts
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ export class TopcoderChallengesService {
}
});

this.logger.debug(`Fetching challenges from: ${url.toString()}`);
this.logger.log(`Fetching challenges from: ${url.toString()}`);

Choose a reason for hiding this comment

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

medium
security
Changing the log level from debug to log may result in more verbose output in production environments. Ensure this change aligns with the intended logging strategy and does not expose sensitive information.


const headers: Record<string, string> = {
'Content-Type': 'application/json',
Expand All @@ -34,7 +34,7 @@ export class TopcoderChallengesService {
headers['Authorization'] = `Bearer ${accessToken}`;
}

this.logger.debug(
this.logger.log(

Choose a reason for hiding this comment

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

medium
maintainability
Changing the log level from debug to log may result in more verbose logging in production environments. Ensure that this change aligns with the intended logging strategy and does not inadvertently expose sensitive information or overwhelm log storage.

`Fetching challenges with headers: ${JSON.stringify(headers)}`,
);

Expand Down