Adding user profile fields

[braydonwang]

Notion Ticket Link

Add User Profile Fields

Implementation Description

• Added additional fields to user schema
• Created custom scalar Date type with its resolver

Steps to Test

1. Nothing at the moment, will need to wait for api endpoints

What should reviewers focus on?

• Look over the resolver and make sure it's right, I followed this doc: https://www.apollographql.com/docs/apollo-server/schema/custom-scalars/

Screenshots (optional)

Checklist

• My PR name is descriptive and in imperative tense
• My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
• I have run the appropriate linter(s)
• I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

Linting & Formatting

Mac

docker exec -it CWC-backend /bin/bash -c "yarn fix"
docker exec -it CWC-frontend /bin/bash -c "yarn fix"

Windows

docker exec -it CWC-backend bash -c "yarn fix"
docker exec -it CWC-frontend bash -c "yarn fix"

[shencynthia]

Just some small changes for consistency and also a nit: use imperative tense for commits + PR (e.g. Add rather than Adding).

Otherwise, looks good!!

[shencynthia]

For the enum in userType you have "InPerson" and here its "In Person".

[shencynthia]

Same thing here, "InPerson" v.s "In Person"

[shencynthia]

LGTM! 👍👍👍

[carolynzhang18]

Is there a reason birthday and locationType are nullable? Ooh actually... nevermind!

I think startDate, birthday, locationType, and headshot should all be nullable (so no ! beside their types) because we don't provide this information to the query on the user's initial signup - the only information we pass when we register a user is their first name & last name, their email, and their password.

The decision between passing all this info to the query at once vs. in multiple steps is probably more of a PM question for later... but for now we should probably keep them nullable so the Sign Up page doesn't break :O

[carolynzhang18]

Same comment as before here: these probably shouldn't be required - the current signup functionality will break :(