The new translation keys are needed for the community type added to Alameda
How Can This Be Tested/Reviewed?
You can't create a listing that has this community type so you will need to pull the prod HBA listings over.
This can be done by going to /tasks/import-listings and run yarn install && yarn build && yarn import:run:local:prod
Then you should see this property:
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
This PR addresses #4113
Description
The new translation keys are needed for the community type added to Alameda
How Can This Be Tested/Reviewed?
You can't create a listing that has this community type so you will need to pull the prod HBA listings over. This can be done by going to
/tasks/import-listingsand runyarn install && yarn build && yarn import:run:local:prodThen you should see this property:
Author Checklist:
yarn generate:clientand/or created a migration when requiredReview Process: