RealDevSquad / RealDevSquad/website-backend
Refactor type enum used in logs collection
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Issue Description
Currently we don't have proper enum for type.
We are using different type of formatting in naming the type to store in logs collection.
Also, we need to refactor the code how it's been used, so migration and refactoring for code has to be taken care from this.
Issue got raised while implementing this feature.
https://github.com/Real-Dev-Squad/website-backend/pull/1976#discussion_r1534294419
Current Behavior
current logs collection have this kind of type, which is not in right format for the constants.
Expected Behavior
With this task have to make the constants for type to be stored in logs collection in same format.
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the discussion linked from PR 1976 and search the backend for logs collection writes and the type values shown in the issue. Define the constants, update their usages, and account for the requested migration so stored log types use one format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100