Skip to content

fix: neighborhood amenities remove sections#5536

Merged
KrissDrawing merged 8 commits into
mainfrom
5477/Neighborhood-Amenities-Remove-Sections
Nov 6, 2025
Merged

fix: neighborhood amenities remove sections#5536
KrissDrawing merged 8 commits into
mainfrom
5477/Neighborhood-Amenities-Remove-Sections

Conversation

@KrissDrawing

@KrissDrawing KrissDrawing commented Nov 4, 2025

Copy link
Copy Markdown
Collaborator

This PR addresses #5477

  • Addresses the issue in full
  • Addresses only certain aspects of the issue

Description

Adds new column in jurisdictions table (visibleNeighborhoodAmenities). It populates as default for current state of amenites.
I got to sligthly refactor NeighborhoodAmenities.tsx so it looks good for each variation (Also changed DetailNeighborhoodAmenities.tsx for consistency).
For seed-staging i've added visibleNeighborhoodAmenities for Angelopolis so it shows just Grocery Stores and Pharmacies (Not sure if i should also add Bus stop field in this task, if so it shouldn't be huge change)

How Can This Be Tested/Reviewed?

Relevant changes in schema.prisma are line 399 and 1300-1309 (rest are just prisma format)
Either run migration, or setup new staging-seed.

  • for angelopolis you should have ability to add just 2 neighborhood amenities (even when you're sneaky and add more, they should not be displayed, and exported)
  • for rest jurisdiction it should work as before
  • For CSV export it will take amenities from all available for user jurisdictions so you need to export from user that has just angelopolis jurisdiction.

Author Checklist:

  • Added QA notes to the issue with applicable URLs
  • Reviewed in a desktop view
  • Reviewed in a mobile view
  • Reviewed considering accessibility
  • Added tests covering the changes
  • Made corresponding changes to the documentation
  • Ran yarn generate:client and/or created a migration when required

Review Process:

  • Read and understand the issue
  • Ensure the author has added QA notes
  • Review the code itself from a style point of view
  • Pull the changes down locally and test that the acceptance criteria is met
  • Either (1) explicitly ask a clarifying question, (2) request changes, or (3) approve the PR, even if there are very small remaining changes, if you don't need to re-review after the updates

@KrissDrawing KrissDrawing added the 1 review needed Requires 1 more review before ready to merge label Nov 4, 2025
@netlify

netlify Bot commented Nov 4, 2025

Copy link
Copy Markdown

Deploy Preview for bloom-public-seeds ready!

Name Link
🔨 Latest commit 50b8cf8
🔍 Latest deploy log https://app.netlify.com/projects/bloom-public-seeds/deploys/690b26632c293c000861e1da
😎 Deploy Preview https://deploy-preview-5536--bloom-public-seeds.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Nov 4, 2025

Copy link
Copy Markdown

Deploy Preview for partners-bloom-dev ready!

Name Link
🔨 Latest commit e05180d
🔍 Latest deploy log https://app.netlify.com/projects/partners-bloom-dev/deploys/690b9a62f7792100075001e5
😎 Deploy Preview https://deploy-preview-5536--partners-bloom-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Nov 4, 2025

Copy link
Copy Markdown

Deploy Preview for bloom-exygy-dev ready!

Name Link
🔨 Latest commit e05180d
🔍 Latest deploy log https://app.netlify.com/projects/bloom-exygy-dev/deploys/690b9a62c4cf5c0008d52016
😎 Deploy Preview https://deploy-preview-5536--bloom-exygy-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Nov 4, 2025

Copy link
Copy Markdown

Deploy Preview for bloom-flagly canceled.

Name Link
🔨 Latest commit e05180d
🔍 Latest deploy log https://app.netlify.com/projects/bloom-flagly/deploys/690b9a62cb739100089d2abf

@netlify

netlify Bot commented Nov 4, 2025

Copy link
Copy Markdown

Deploy Preview for bloom-lakeview ready!

Name Link
🔨 Latest commit 50b8cf8
🔍 Latest deploy log https://app.netlify.com/projects/bloom-lakeview/deploys/690b2663c9d2910008eafc11
😎 Deploy Preview https://deploy-preview-5536--bloom-lakeview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@KrissDrawing KrissDrawing changed the title 5477/neighborhood amenities remove sections fix: neighborhood amenities remove sections Nov 4, 2025

@emilyjablonski emilyjablonski left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This is awesome! My only comments are non-blocking on style.

There is one UI state I think we should adjust, which is before you have selected a jurisdiction, it shows as an empty section. We keep running into cases like this as we change behavior across jurisdictions and eventually will likely make a user pre-select a jurisdiction before they ever get to the edit page. But, for now I'd recommend we not show the section at all until we have a jurisdiction, as a jurisdiction could have no amenities at all or have the feature flag disabled.

Image

@emilyjablonski emilyjablonski added needs changes The author must make changes and then re-request review before merging and removed 1 review needed Requires 1 more review before ready to merge labels Nov 4, 2025
@emilyjablonski

Copy link
Copy Markdown
Collaborator

We can also wait on bus stops as we have this ticket comin up: #5498

@KrissDrawing KrissDrawing added 1 review needed Requires 1 more review before ready to merge and removed needs changes The author must make changes and then re-request review before merging labels Nov 5, 2025

@emilyjablonski emilyjablonski left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

🥳

@emilyjablonski emilyjablonski added ready to merge Should be applied when a PR has been reviewed and approved and removed 1 review needed Requires 1 more review before ready to merge labels Nov 5, 2025
@KrissDrawing KrissDrawing merged commit c3f76c5 into main Nov 6, 2025
30 checks passed
@KrissDrawing KrissDrawing deleted the 5477/Neighborhood-Amenities-Remove-Sections branch November 6, 2025 06:22
mcgarrye added a commit to metrotranscom/doorway that referenced this pull request Nov 6, 2025
* feat: add visible neighborhood amenities to jurisdictions and update related components

* fix: add option to seed visibleNeighborhoodAmenities

* fix: show just visible neighborhood amenities in csv export

* test: fix

* refactor: use enum to map amenities

* fix: hide neighborhood amenities section when no jurisdiction selected

---------

Co-authored-by: Emily Jablonski <65367387+emilyjablonski@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready to merge Should be applied when a PR has been reviewed and approved

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants