Skip to content

Conversation

@chromium-52
Copy link
Member

ℹ️ Issue

Closes

📝 Description

Write a short summary of what you added. Why is it important? Any member of C4C should be able to read this and understand your contribution -- not just your team members.

Briefly list the changes made to the code:

  1. Added support for this.
  2. And removed redunant use of that.
  3. Also this was included for reasons.

✔️ Verification

What steps did you take to verify your changes work? These should be clear enough for someone to be able to clone the branch and follow the steps themselves.

Provide screenshots of any new components, styling changes, or pages.

🏕️ (Optional) Future Work / Notes

Did you notice anything ugly during the course of this ticket? Any bugs, design challenges, or unexpected behavior? Write it down so we can clean it up in a future ticket!

chromium-52 and others added 10 commits October 30, 2023 16:20
* feat: completed updateUser endpoint resolves #5

* style: used strict comparison operators and modified error messages

* added error handling for objectID

* feat: added input validation to UpdateUserDTO

* fix: applied suggestions from PR review

* fix: added domain specific URL validators for DTO

* fix: converted ObjectId primary column to numbers and finalized PR suggestions

* fix: strict equality and https restricted protocol

---------

Co-authored-by: Harrison Kim <kim.harr@northeastern.edu>
* worked on getUser method and user parameters
---------

Co-authored-by: Kenny Jung <dukyoung01@naver.com>
@chromium-52 chromium-52 deleted the kjung/fix-setup-auth-followup branch February 22, 2024 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants