RealDevSquad / RealDevSquad/website-backend
Create a check in addOrUpdate function to avoid unexpected types and fields in profileDiffs
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Issue Description
In addOrUpdate function in users which updates profileDiffs, we need to check that the profileDiffs does not contain wrong types like null and undefined.
Expected Behavior
Throws an error if profileDiffs contains undefined or null type value
Current Behavior
Not Handled
Screenshots
Severity/Priority
- Critical
- High
- Medium
- Low
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
Locate the addOrUpdate entry point in users and read how profileDiffs is currently updated. Check the expected error behavior for null and undefined values, and consider the work done when those values are rejected as specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100