fix: neighborhood amenities remove sections#5536
Conversation
✅ Deploy Preview for bloom-public-seeds ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for partners-bloom-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-flagly canceled.
|
✅ Deploy Preview for bloom-lakeview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
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.
|
We can also wait on bus stops as we have this ticket comin up: #5498 |
* 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>
This PR addresses #5477
Description
Adds new column in jurisdictions table (visibleNeighborhoodAmenities). It populates as default for current state of amenites.
I got to sligthly refactor
NeighborhoodAmenities.tsxso it looks good for each variation (Also changedDetailNeighborhoodAmenities.tsxfor consistency).For seed-staging i've added visibleNeighborhoodAmenities for
Angelopolisso it shows justGrocery StoresandPharmacies(Not sure if i should also addBus stopfield in this task, if so it shouldn't be huge change)How Can This Be Tested/Reviewed?
Relevant changes in
schema.prismaare line 399 and 1300-1309 (rest are justprisma format)Either run migration, or setup new staging-seed.
angelopolisjurisdiction.Author Checklist:
yarn generate:clientand/or created a migration when requiredReview Process: