RealDevSquad / RealDevSquad/website-backend

Error logging should be more detailed

Open
#1,861 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
74
Forks
276
Avg merge
1d 26m
Merged PRs (30d)
14

Description

Issue Description

Missing Error Details: The logged error message only includes ${err}, which might not provide sufficient information for debugging. We can Consider logging more specific details about the error, such as the error type, stack trace, and relevant variables.
Eg
logger.error(Error while deleting role: ${error});
https://github.com/Real-Dev-Squad/website-backend/pull/1848/#discussion_r1459938205

This need more discussion

Expected Behavior
Current Behavior
Screenshots
Reproducibility
  • This issue is reproducible
  • This issue is not reproducible
Steps to Reproduce
Severity/Priority
  • Critical
  • High
  • Medium
  • Low
Additional Information
Checklist
  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the discussion linked from pull request 1848 and identify the agreed scope for more detailed error logging. Then locate the affected deletion logging path in the backend and define done as logging the agreed error details without exposing inappropriate information; the issue names no file or test to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
backend, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.