RealDevSquad / RealDevSquad/website-backend

separate validator functions for better testing

Open
#1,797 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

[Provide a brief description of the issue here.]

Expected Behavior

[Describe what should happen when this issue is resolved.]

Current Behavior

[Explain what currently happens when this issue is encountered.]

Screenshots

[If applicable, add screenshots or images that help illustrate the issue. You can use the following Markdown syntax to embed images:]

Reproducibility
  • This issue is reproducible
  • This issue is not reproducible
Steps to Reproduce
  1. [Step 1]
  2. [Step 2]
Severity/Priority
  • Critical
  • High
  • Medium
  • Low
Additional Information

[Include any additional context, logs, or details that might be helpful in addressing the issue.]

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.

Thank you for contributing to our project! We appreciate your help in improving it.

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

The issue names no files, tests, or entry points, and its body contains only the unfilled issue template. Begin by locating the validator logic in the backend and determine which functions should be separated. Done means the validators are independently testable, but the expected behavior is not specified here.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.