Closed ColinBuyck closed 4 months ago
Name | Link |
---|---|
Latest commit | 9cf9b3c1e883cb35cfc5b9fa7bcf4f164a5c047f |
Latest deploy log | https://app.netlify.com/sites/partners-bloom-dev/deploys/6672137954e1920008257483 |
Deploy Preview | https://deploy-preview-4148--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 | 9cf9b3c1e883cb35cfc5b9fa7bcf4f164a5c047f |
Latest deploy log | https://app.netlify.com/sites/bloom-exygy-dev/deploys/667213798252ba0008842c68 |
Deploy Preview | https://deploy-preview-4148--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 #4147
Description
This PR adds in language to the headers of the listings call on the preview page so that it matches the [slug.tsx] headers. This way the translation service is called within the listingService.findOne() call.
How Can This Be Tested/Reviewed?
This can be tested by pulling this down locally, previewing a listing from the partner's side and see that most if not all strings are translating with the exception of a few particular fields such as "or one month's rent may be higher for lower credit scores" which are known by Sarah. If you wish you can uncomment the new line to see the difference.
Author Checklist:
yarn generate:client
and/or created a migration when requiredReview Process: