-
Notifications
You must be signed in to change notification settings - Fork 26
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: update label for monthly minimum income #3609
fix: update label for monthly minimum income #3609
Conversation
✅ Deploy Preview for bloom-demo-public 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. |
@sarahlazarich in task we have 2 versions of that string. In title there is |
@KrissDrawing can we actually use "minimum monthly income"? Apologies for the discrepancy there. |
✅ Deploy Preview for bloom-partners-listings-approval ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
* feat: update label for monthly minimum income * fix: change string to Minimum Monthly Income
* chore(deps): bump http-cache-semantics from 4.1.0 to 4.1.1 (bloom-housing#3522) * chore(deps): bump fast-xml-parser from 4.1.3 to 4.2.4 (bloom-housing#3500) * chore(deps): bump @sideway/formula from 3.0.0 to 3.0.1 (bloom-housing#3354) * fix: remove updated_at field from listing details page (bloom-housing#3527) * feat: uptake field value v2 (bloom-housing#3509) * fix: partners listings table sort by status (bloom-housing#3576) * fix: add sorting by status * fix: change default sort to status * fix: default sorting by status * fix: sort by application when the same status * fix: orderBy test using default value * fix: trigger backend sorting on initial load * fix: add unsort icon to indicate that column might be sorted * test: rollback test changes * fix: use enums to order by status * chore: upgrade uic * refactor: use new seeds tag component (bloom-housing#3597) * feat: submit for approval flow (bloom-housing#3598) * fix: cors origin deploy preview issues (bloom-housing#3564) * fix: update label for monthly minimum income (bloom-housing#3609) * feat: update label for monthly minimum income * fix: change string to Minimum Monthly Income * feat: listings approval superadmin flow (bloom-housing#3611) * fix: add backend url validation for url fields (bloom-housing#3568) * fix: add backend url validation for url fields * fix: validate only if externalUrl should be URL * fix: use form values for application types on failed form submit * fix: hide url field when no digital application * fix: set proper default value to common digital application choice * fix: add hasHttps decorator for second error variant * fix: add four and five bedrooms keys to sort array (bloom-housing#3618) * fix: sort table with listings approval statuses (bloom-housing#3622) * test: add listings approval cypress tests (bloom-housing#3612) * feat: listings approval emails (bloom-housing#3600) * fix: use primary tag variants in partners (bloom-housing#3632) * fix: amiPercentage being unset on unit edit (bloom-housing#3635) --------- Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Krzysztof Zięcina <kziecina@airnauts.com> Co-authored-by: Emily Jablonski <65367387+emilyjablonski@users.noreply.github.com> Co-authored-by: ColinBuyck <53269332+ColinBuyck@users.noreply.github.com> Co-authored-by: Yazeed Loonat <YazeedLoonat@gmail.com>
Pull Request Template
Issue Overview
This PR addresses #3567
Description
Changes label for
Monthly Minimum Income
on partners site.How Can This Be Tested/Reviewed?
go to edit listing in partners site -> add unit -> select
fixed amount
first label should beMonthly Minimum Income
.In listing details page click
view
on unit that has above filled. It should also beMonthly Minimum Income
now.Checklist:
yarn generate:client
and/or created a migration if I made backend changes that require themReviewer Notes:
Steps to review a PR:
On Merge:
If you have one commit and message, squash. If you need each message to be applied, rebase and merge.