Partners - FE/BE - Region and Neighborhood

[emilyjablonski]

These two fields (Region and Neighborhood) exist in the partners site and display to the right of building address:

We need to add the "Region" and the "Neighborhood" fields to the address section.

Note: this solution will only work for Detroit Regions and neighborhoods. We will follow-up later with a more dynamic option

Steps needed for Region:

Create a new feature flag for this feature enableRegions

• Backend:
  • Add "region" to the listing.dto.ts
    • Value of the RegionEnum. Make sure this is exposed in the swagger doc
  • Update listing create endpoint to save the region when it exists in the dto
  • Update listing edit endpoint to save the region when it exists in the dto
  • Update/verify that the listing get endpoints returns the "region" field
  • Add the "region" field to the CSV export
    • The column should only exist if the feature flag is turned on at least one jurisdiction user has access to
• Frontend:
  • Add the new field in the "Building Address " section to the right of the zipcode
    • This should be behind the new feature flag
    • When it shows, the "Year Built" field will get moved to the next line
    • The list of options can use the DB RegionEnum exposed in the swagger doc

Steps needed for Neighborhood:

Currently in Core, we do already have a Neighborhood field that is an open text input. However, in Detroit this field is a drop down with limited specific inputs that are used to filter in Detroit.

• Backend:
  • No changes are needed for this ticket
• Frontend:
• When the above feature flag is set to true for the jurisdiction change the "neighborhood" field from an input to a drop down
  • Values for the dropdown can be hardcoded for now in the partner site similar to how Detroit does it
  • If the value of the "neighborhood" select is changed, the "region" should also change to the mapped region
  • If the value of the "region" is change the "neighborhood" value should clear

AC:

In core:

• With the region toggle on, partner users can enter a region on a listing.
• With the region toggle on, partner users can select a neighborhood from a pre-created list
• With the region toggle on, if a partner user changes the "neighborhood" the "region" changes to the corresponding region
• With the region toggle on, if a partner user changes the "region" the "neighborhood" entry clears
• With the region toggle off, partner users can enter any neighborhood into the field
• A listing with a neighborhood and region will show up in the listing csv export

[emilyjablonski]

@ludtkemorgan Noticed this one was missing - want to make sure we do intend to bring it over! If not I can close. I'm not sure how we would handle the typing as it is an enum now

[ludtkemorgan]

@emilyjablonski nice catch. Looks like I missed this. I think we need to have a mini spike to see how we can handle the enums as the long term solution they shouldn't be hardcoded. I'll create a subtask for that

[sarahlazarich]

@emilyjablonski do we need designs for this, or would this be ready to pull in?

[sarahlazarich]

Question for @emilyjablonski and @eajensenwa :

• Will we ever need to show the application date into in the right rail?

[emilyjablonski]

@sarahlazarich Yes we do this already (if I'm understanding correctly) like in this listing: https://housingbayarea.mtc.ca.gov/listing/ec69bcb8-8334-4c3b-9756-46cd466dcfd8/riviera_family_apartments_1515_riviera_ave_walnut_creek_ca