Skip to content

Description page for each Couple Type enhancement New feature or request frontend Codes that affects frontend#4

Open
evanwang9x wants to merge 11 commits intomainfrom
Evan/Couple-Type-Component
Open

Description page for each Couple Type enhancement New feature or request frontend Codes that affects frontend#4
evanwang9x wants to merge 11 commits intomainfrom
Evan/Couple-Type-Component

Conversation

@evanwang9x
Copy link
Contributor

@evanwang9x evanwang9x commented Jun 27, 2025

Done with issue#1
Contents of this component depends on what it has been called with. For now it defaults to homebody cause I have no clue how calling logic will work in the future
Screenshot 2025-06-26 at 9 51 33 PM

Dropdown component. I'll worry about improving its aesthetics when the design team gets around to it
Screenshot 2025-06-28 at 10 15 45 AM

Part of the http://localhost:3000/type page.

Screen.Recording.2025-06-30.at.11.42.44.AM.mov

@huajie-zhong huajie-zhong added enhancement New feature or request frontend Codes that affects frontend labels Jun 27, 2025
@huajie-zhong huajie-zhong linked an issue Jun 27, 2025 that may be closed by this pull request
@evanwang9x evanwang9x changed the title Added aa component to display results Added a component to display results Jun 28, 2025
@evanwang9x evanwang9x changed the title Added a component to display results Description page for each Couple Type enhancement New feature or request frontend Codes that affects frontend Jun 28, 2025
@huajie-zhong huajie-zhong deleted the branch main August 5, 2025 03:21
@huajie-zhong huajie-zhong reopened this Aug 5, 2025
@huajie-zhong huajie-zhong changed the base branch from backend-schema-setup to main August 5, 2025 03:28
@huajie-zhong
Copy link
Contributor

I don't know why github UI didn't offer any easier way. But here is what happened: I was clearing outdated merged branch, but I realized that it automatically closes this PR as the branch was the branch to merge into, so I had to restore the branch to reopen and change base branch.
In short, every thing is fixed. No worry about the mess I made above. I will start looking at this PR

@huajie-zhong huajie-zhong force-pushed the Evan/Couple-Type-Component branch from 341799b to 881efcb Compare October 27, 2025 01:20
@huajie-zhong
Copy link
Contributor

Hi Evan, I've just rebased your branch with the most up to date edits and color schema. I think the design team also has a high fidelity design ready for the Couple types, can you please look into Figma and update accordingly?

Also a small bug, likely due to z-index, the navigation is being covered by the main page elements.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request frontend Codes that affects frontend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Description page for each Couple Type

2 participants