Skip to content

Add Timezones To Intake Form#66

Merged
YashK2005 merged 7 commits intomainfrom
yash/add-timezones-to-intake
Nov 11, 2025
Merged

Add Timezones To Intake Form#66
YashK2005 merged 7 commits intomainfrom
yash/add-timezones-to-intake

Conversation

@YashK2005
Copy link
Collaborator

@YashK2005 YashK2005 commented Oct 31, 2025

1. Added Timezone dropdown to intake form

  • migration to add time_zone column to user_data table
  • updated intake_form_processor to store timezone in the new column
  • added timezone dropdown to the intake form
  • timezoneUtils.ts - automatically detects the user's timezone when they load the intake form and prefills the timezone dropdown if possible

2. Updated onboarding form styling to match Figma

  • updated dropdowns for marital status and ethnic group to match actual option list
  • added 2 new components for dropdowns that match the figma styling
  • updated borders of text input fields to match figma styling

Notion ticket link

Time Zones

Implementation description

Steps to test

What should reviewers focus on?

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

@YashK2005
Copy link
Collaborator Author

@codex review

@chatgpt-codex-connector
Copy link

Codex Review: Didn't find any major issues. What shall we delve into next?

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@YashK2005 YashK2005 force-pushed the yash/add-timezones-to-intake branch from d4eabf2 to 1830a28 Compare November 10, 2025 06:18
@YashK2005 YashK2005 merged commit 872fe21 into main Nov 11, 2025
5 checks passed
@YashK2005 YashK2005 deleted the yash/add-timezones-to-intake branch November 11, 2025 00:19
UmairHundekar pushed a commit that referenced this pull request Nov 25, 2025
#### 1. Added Timezone dropdown to intake form
- migration to add time_zone column to user_data table
- updated intake_form_processor to store timezone in the new column
- added timezone dropdown to the intake form
- timezoneUtils.ts - automatically detects the user's timezone when they
load the intake form and prefills the timezone dropdown if possible

#### 2. Updated onboarding form styling to match Figma
- updated dropdowns for marital status and ethnic group to match actual
option list
- added 2 new components for dropdowns that match the figma styling
- updated borders of text input fields to match figma styling

## Notion ticket link
<!-- Please replace with your ticket's URL -->
[Time
Zones](https://www.notion.so/uwblueprintexecs/Time-Zones-29410f3fb1dc80f8819ee5616c42aa3c?v=27210f3fb1dc8133a6e1000cf4eabc81&source=copy_link)


<!-- Give a quick summary of the implementation details, provide design
justifications if necessary -->
## Implementation description
* 


<!-- What should the reviewer do to verify your changes? Describe
expected results and include screenshots when appropriate -->
## Steps to test
1.


<!-- Draw attention to the substantial parts of your PR or anything
you'd like a second opinion on -->
## What should reviewers focus on?
* 


## 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
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.

1 participant