Skip to content

add more logs #11

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

add more logs #11

merged 1 commit into from
Jul 10, 2025

Conversation

vas3a
Copy link
Collaborator

@vas3a vas3a commented Jul 10, 2025

No description provided.

@vas3a vas3a merged commit 54d9aca into dev Jul 10, 2025
1 check passed
@vas3a vas3a deleted the logger-level-for-challenges branch July 10, 2025 16:06
headers,
});
try {
return await fetch(stringUrl, {

Choose a reason for hiding this comment

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

high
correctness
The await keyword is used here, but the function is not marked as async. This will result in a syntax error. Ensure the function is declared as async to handle the await correctly.

headers,
});
} catch (error) {
this.logger.error(`Error fetching challenges: ${JSON.stringify(error)}`, error);

Choose a reason for hiding this comment

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

medium
readability
Consider using error.message instead of JSON.stringify(error) for logging the error message. JSON.stringify might not serialize the error object as expected, leading to loss of information.

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.

1 participant