Closed ludtkemorgan closed 2 months ago
Name | Link |
---|---|
Latest commit | fd0803f732417179d8804fc07ef4f9f3d844cbb4 |
Latest deploy log | https://app.netlify.com/sites/partners-bloom-dev/deploys/6678a5850235b900089b80d7 |
Deploy Preview | https://deploy-preview-4153--partners-bloom-dev.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Name | Link |
---|---|
Latest commit | fd0803f732417179d8804fc07ef4f9f3d844cbb4 |
Latest deploy log | https://app.netlify.com/sites/bloom-exygy-dev/deploys/6678a58587ec520008a044a0 |
Deploy Preview | https://deploy-preview-4153--bloom-exygy-dev.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
This PR addresses #4140
Description
When a reserved community type already exists on a listing and should be removed it was not properly being removed because it needs to be "disconnected" rather than just set to undefined
How Can This Be Tested/Reviewed?
Add a community type to a listing and save the listing. Then re-edit the listing and remove the reserved community type. The community type should no longer be on the listing
Author Checklist:
yarn generate:client
and/or created a migration when requiredReview Process: