Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show component work types in component list items #1479

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

chiaberry
Copy link
Member

@chiaberry chiaberry commented Nov 8, 2024

Associated issues

cityofaustin/atd-data-tech#19560

Testing

URL to test:
https://deploy-preview-1479--atd-moped-main.netlify.app/moped/projects/2049?tab=map&project_component_id=2686

Steps to test:

Expand components and see the work type in a gray chip

Screenshot 2024-11-11 at 8 45 30 AM


Ship list

  • Code reviewed
  • Product manager approved
  • Product manager checked DB view dependencies
  • Product manager added to QA test script if applicable
    • Added to component focus test - "You should see chips with the component works types in the expanded list item."

@chiaberry chiaberry added the Type: Enhancement Request for an improvement to existing functionality in an application label Nov 8, 2024
Copy link
Collaborator

@mddilley mddilley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I requested a couple tiny spacing adjustments, and then this is 🚢. Looks great, and it is good to see these component details in the expanded item!

Copy link
Collaborator

@mddilley mddilley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!!! Good to see these work types in the list items. 🚀 🙌

@@ -107,6 +121,18 @@ export default function ComponentListItem({
/>
</ListItem>
)}
<ListItem className={classes.workTypeGroup}>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small detail, but this class is now a duplicate of the existing nested one.

Copy link
Member

@johnclary johnclary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested on the deploy preview, and it looks great. I love chips!

One minor detail is that clicking related-project components now causes them to expand ever so slightly:

Screenshot 2024-11-12 at 1 32 33 PM

See john's ironweed project (edited) for example.

@chiaberry
Copy link
Member Author

@johnclary ah because those are components that were either migrated or added before we had the requirement to include a work type

@mddilley should I conditionally show the ListItem if there is a component work type? Since its required, i assumed it would always show up, but theres probably a number of components with no type

@mddilley
Copy link
Collaborator

@chiaberry Yes, I think that we should conditionally render like we do for the description below it. Thanks for catching that @johnclary! 🙏

@johnclary johnclary self-requested a review November 18, 2024 19:03
Copy link
Member

@johnclary johnclary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢 🚢 🚢 🚢 🚢 🚢 🚢 🚢 🚢 🚢

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Request for an improvement to existing functionality in an application
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants