-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: add home type feature to backend and partners #4484
Conversation
✅ Deploy Preview for partners-bloom-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
376ed4f
to
4da746a
Compare
4da746a
to
3bfde07
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are accessibility issues in these changes.
sites/partners/src/components/listings/PaperListingForm/sections/Units.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are accessibility issues in these changes.
sites/partners/src/components/listings/PaperListingForm/sections/Units.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! 1 small nit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't peeked at the code yet, but a few functionality notes!
I think I would expect that between the detail and edit view, that the fields are in the same order - it looks like the new field is in each view above and then below the neighbor fields.
And then when I select a value and save it, it shows as saved on the detail page, but if I reopen the edit page, it doesn't populate with the value.
sites/partners/src/components/listings/PaperListingDetails/sections/DetailUnits.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are accessibility issues in these changes.
sites/partners/src/components/listings/PaperListingForm/sections/Units.tsx
Show resolved
Hide resolved
da215b3
to
1d0179b
Compare
@emilyjablonski Thanks for the review. Looks like I accidentally introduced the issue where the home type doesn't persist when editing with the useEffect. This has been fixed and you should be able to see the selected home type now. I'll need to reach out to design about where to place the home type field as it doesn't really make a lot of sense in either of the spots. For now I updated the field to be in the same place for both edit and detail view |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I got confirmation from Em that the placement of the field is fine. We can revisit it if any non-detroit jurisdiction ever wants it |
* fix: add hometype to listing create/update * fix: add home type to csv * fix: update jwt to retrieve feature flags * fix: partner changes * fix: have partner be behind feature flag * fix: backend test fix * fix: remove comment * fix: address comments * fix: review comments
… (#830) * fix: add hometype to listing create/update * fix: add home type to csv * fix: update jwt to retrieve feature flags * fix: partner changes * fix: have partner be behind feature flag * fix: backend test fix * fix: remove comment * fix: address comments * fix: review comments
* fix: add hometype to listing create/update * fix: add home type to csv * fix: update jwt to retrieve feature flags * fix: partner changes * fix: have partner be behind feature flag * fix: backend test fix * fix: remove comment * fix: address comments * fix: review comments
* fix: add hometype to listing create/update * fix: add home type to csv * fix: update jwt to retrieve feature flags * fix: partner changes * fix: have partner be behind feature flag * fix: backend test fix * fix: remove comment * fix: address comments * fix: review comments
* fix: add hometype to listing create/update * fix: add home type to csv * fix: update jwt to retrieve feature flags * fix: partner changes * fix: have partner be behind feature flag * fix: backend test fix * fix: remove comment * fix: address comments * fix: review comments
* fix: add hometype to listing create/update * fix: add home type to csv * fix: update jwt to retrieve feature flags * fix: partner changes * fix: have partner be behind feature flag * fix: backend test fix * fix: remove comment * fix: address comments * fix: review comments
This PR addresses #4432, #4431
Description
Adds the "Home Type" select option to the listing create/edit page as well as connecting HomeType to the listing create endpoint, edit endpoint, and the CSV export.
This is also the first feature using the new feature flag table so some extra logic to utilize it has been added
NOTES:
How Can This Be Tested/Reviewed?
Other things you can test:
Author Checklist:
yarn generate:client
and/or created a migration when requiredReview Process: