Skip to content

Conversation

@ludtkemorgan
Copy link
Collaborator

@ludtkemorgan ludtkemorgan commented Jan 27, 2026

This PR addresses #5380 #5749

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

Description

This tackles the following issues for non-regulated listings

  1. The preferred unit question on both public and partner application forms was never being shown. This is due to non-regulated unit groups do not have the "waitlist status" question which was the determinator for if a unit type was shown or not. The new logic is to only look at the waitlist status if the listing is not of type "nonRegulated"
  2. Typos in the description of regulated vs non-regulated listings
  3. With a recent un-related change the "regions" field was accidentally removed for non-regulated instead of the "year built" field
  4. Listings occasionally switched from non-regulated to "regulated" when opening up the listing edit page. This is due to the edit page using the form value instead of the listing's value of "listingType".

How Can This Be Tested/Reviewed?

Preferred unit

  1. Create a non-regulated listing. Add at least one unit group to it and make sure the common app is set for the listing
  2. Go to the public site and apply to the new listing
  3. When you get to the /household/preferred-units page of the form you should see all of the unit types attached to the listing. (Note this page was not appearing previously)
  4. Go to the partner site and apply to the listing. The preferred unit type question should be on the form.

regions

  1. In partners create a non-regulated listing. The regions field should appear (if enableRegions feature flag is turned on) and the "Year built" should not appear

Typos

  1. Click "add listing", select "Lakeview". The listing type question should appear and the text should be updated properly

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

@netlify
Copy link

netlify bot commented Jan 27, 2026

Deploy Preview for partners-bloom-dev ready!

Name Link
🔨 Latest commit ee0618c
🔍 Latest deploy log https://app.netlify.com/projects/partners-bloom-dev/deploys/697a798b7b6e690008412518
😎 Deploy Preview https://deploy-preview-5794--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
Copy link

netlify bot commented Jan 27, 2026

Deploy Preview for bloom-exygy-dev ready!

Name Link
🔨 Latest commit ee0618c
🔍 Latest deploy log https://app.netlify.com/projects/bloom-exygy-dev/deploys/697a798bd38bce0008159213
😎 Deploy Preview https://deploy-preview-5794--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
Copy link

netlify bot commented Jan 27, 2026

Deploy Preview for bloom-flagly ready!

Name Link
🔨 Latest commit ee0618c
🔍 Latest deploy log https://app.netlify.com/projects/bloom-flagly/deploys/697a798c2cf64d00083f7c8f
😎 Deploy Preview https://deploy-preview-5794--bloom-flagly.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
Copy link

netlify bot commented Jan 27, 2026

Deploy Preview for bloom-public-seeds ready!

Name Link
🔨 Latest commit ee0618c
🔍 Latest deploy log https://app.netlify.com/projects/bloom-public-seeds/deploys/697a798d60241200086b2834
😎 Deploy Preview https://deploy-preview-5794--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
Copy link

netlify bot commented Jan 27, 2026

Deploy Preview for bloom-angelopolis canceled.

Name Link
🔨 Latest commit ee0618c
🔍 Latest deploy log https://app.netlify.com/projects/bloom-angelopolis/deploys/697a798bde0e080008529e4b

@netlify
Copy link

netlify bot commented Jan 27, 2026

Deploy Preview for bloom-lakeview ready!

Name Link
🔨 Latest commit ee0618c
🔍 Latest deploy log https://app.netlify.com/projects/bloom-lakeview/deploys/697a798bd1bbaa0009e72cf5
😎 Deploy Preview https://deploy-preview-5794--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.

@ludtkemorgan ludtkemorgan force-pushed the non-regulated-regions branch from 47b85d2 to bf53d28 Compare January 28, 2026 19:24
@ludtkemorgan ludtkemorgan changed the title fix: enable regions for non-regulated fix: non-regulated preferred units Jan 28, 2026
@ludtkemorgan ludtkemorgan force-pushed the non-regulated-regions branch from bf53d28 to e72fd9a Compare January 28, 2026 19:58
@ludtkemorgan ludtkemorgan marked this pull request as ready for review January 28, 2026 20:00
@ludtkemorgan ludtkemorgan added the 1 review needed Requires 1 more review before ready to merge label Jan 28, 2026
@ludtkemorgan ludtkemorgan force-pushed the non-regulated-regions branch from e72fd9a to ee0618c Compare January 28, 2026 21:03
import { screen, within } from "@testing-library/react"
import { FormProviderWrapper, mockNextRouter, render } from "../../../../testUtils"
import BuildingDetails from "../../../../../src/components/listings/PaperListingForm/sections/BuildingDetails"
import { EnumListingListingType } from "@bloom-housing/shared-helpers/src/types/backend-swagger"
Copy link
Collaborator

Choose a reason for hiding this comment

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

nitpick (non-blocking): can scoot this import up

listingSectionQuestions,
} from "@bloom-housing/shared-helpers"
import {
EnumListingListingType,
Copy link
Collaborator

Choose a reason for hiding this comment

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

question: Curious why Listing is repeated here

import ApplicationConductor from "../../../../src/lib/applications/ApplicationConductor"
import { AppSubmissionContext } from "../../../../src/lib/applications/AppSubmissionContext"
import { AuthProvider, blankApplication } from "@bloom-housing/shared-helpers"
import {
Copy link
Collaborator

Choose a reason for hiding this comment

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

nitpick (non-blocking): can scoot these imports up

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

Labels

1 review needed Requires 1 more review before ready to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants