You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When viewing the deceased contacts list page a warning is displayed in the console Translation for contact.deceased doesn't exist. Adding a key value for contact.deceased to your language file doesn't seem to get used but does clear the error.
To Reproduce
Steps to reproduce the behavior:
Add a person who is deceased using the CHT/default config.
Navigate to the deceased list page.
The console displays the warning Translation for contact.deceased doesn't exist. is shown.
Add a key value for contact.deceased to your language file and upload.
The warning is removed but that isn't displayed.
Expected behavior
I'm not real sure what that value is supposed to be used for. Might be worth just removing.
Environment
Instance: gamma.dev
Browser: chrome
Client platform: linux
App: webapp
Version: 3.7
Additional context
Add any other context about the problem here. What have you tried? Is there a workaround?
The text was updated successfully, but these errors were encountered:
It's used in the title bar when viewing a deceased person which is only shown on mobile. We have a similar translation key "contact.deceased.title = Deceased" defined in the main translation file which I think we should use here instead of introducing another translation key. Either way we should not ship with translations missing, so let's get this fixed.
Describe the bug
When viewing the deceased contacts list page a warning is displayed in the console
Translation for contact.deceased doesn't exist
. Adding a key value forcontact.deceased
to your language file doesn't seem to get used but does clear the error.To Reproduce
Steps to reproduce the behavior:
Translation for contact.deceased doesn't exist
. is shown.contact.deceased
to your language file and upload.Expected behavior
I'm not real sure what that value is supposed to be used for. Might be worth just removing.
Environment
Additional context
Add any other context about the problem here. What have you tried? Is there a workaround?
The text was updated successfully, but these errors were encountered: