Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Missing fields for user

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
mongodb
Domain
api, database

Research direction

Review the linked Zeplin profile design and the existing user data model. Trace the create-user and update-user API paths to identify where the four missing profile fields and the two legal agreements belong. Done means the data model and both API operations support the specified fields, with agreement metadata represented as decided by the project.

Written by the indexing model from the issue text.

Description

There are some fields shown in the design to create a user "profile" (complete your profile after registration) that are currently not supported by the data model. See https://app.zeplin.io/project/5ebb0c7bc826984e0abb929b/screen/5ebf49b28518062fa64e2232

These should probably also be added to the data model & API to create user & update user.

The fields that we discussed for legal, shown as these 2 required checkboxes:

  • By signing up, I agree to the Privacy Policy
  • By signing up, I agree to the Terms and Conditions
    These could be saved with a timestamp or version instead of just a boolean to add some useful metadata.

The other 2 fields that are missing are also 2 check boxes and might need to be added to the data model:

  • I am travelling
  • Don't show my address
Dominant language
HTML
Stars
6
Forks
1
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from FightPandemics/DataModel

All issues in FightPandemics/DataModel

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.