Implemented User model

[codingmickey]

Regarding #41 are there any more fields required?

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
memories-app	✅ Ready (Inspect)	Visit Preview	Sep 19, 2022 at 5:16PM (UTC)
memories-app-server	✅ Ready (Inspect)	Visit Preview	Sep 19, 2022 at 5:16PM (UTC)

[shreya024]

Regarding #41 are there any more fields required?

Messages,Bookmarks,followers,following

[Debdeep1]

Regarding #41 are there any more fields required?

All these updates are working fine on your localhost?

[shreya024]

@codingmickey Add the new fields so I can merge the PR

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

| GitGuardian id | Secret | Commit | Filename | | | -------------- | ------------------------- | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/incidents/secrets) | MongoDB Credentials | d06dbd0ef6562c5e735e31af67a7e995139a9680 | server/index.js | [View secret](https://github.com/shreya024/MemoriesApp/commit/d06dbd0ef6562c5e735e31af67a7e995139a9680#diff-0861d6d6b50d7d695344bf2d86d6e5e6L20) |

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/detectors/specifics/mongo_uri#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data. To avoid such incidents in the future consider - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/internal-repositories-monitoring/integrations/git_hooks/pre_commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[codingmickey]

@shreya024 How does this look now? sorry for such a delayed reply as was very busy in some college procedures

[shreya024]

@shreya024 How does this look now? sorry for such a delayed reply as was very busy in some college procedures

No problem. Under review now