JHipster i18n for entity not being used - internationalization

Question

I have a a JHipster application and I can see that the UI has all the field labels ok as some sort of defaults. But I also see that the entity specific translations are not being used.
I have a file src/main/webapp/i18n/en/employee.json for example,
{
"myApp": {
"employee": {
"home": {
"title": "Employees",
"createLabel": "Create a new Employee TEST TEST",
"createOrEditLabel": "Create or edit an Employee",
"notFound": "No Employees found"
},
"created": "A new Employee is created with identifier {{ param }}",
"updated": "An Employee is updated with identifier TEST TEST {{ param }}",
"deleted": "An Employee is deleted with identifier {{ param }}",
"delete": {
"question": "Are you sure you want to delete Employee {{ id }}?"
},
"detail": {
"title": "Employee"
},
"Employee": "Employee",
}
}
}
The create label just says "Create a new Employee", not "Create a new Employee TEST TEST".
Also, when I save an entity, I am seeing translation-not-found[A employee is updated with identifier 1]
Adding information suggested to Gaël Marziou.
Does it work when you restart webpack dev server npm start?
I start my server. In a terminal, I do npm start.
Webpack: Finished after 35.767 seconds.
DONE Compiled successfully in 35797ms 12:50:47 PM
No type errors found
Version: typescript 3.4.5
Same error: translation-not-found[A employee is updated with identifier 1].
What are the keys in your HTML templates?
There is a file employee.component.html and it uses keys:
myApp.employee.home.title
myApp.employee.home.createLabel
myApp.employee.home.notFound
global.field.id
myApp.employee.name
entity.action.view
entity.action.edit
entity.action.delete
but in no file so I see the use of myApp.employee.updated - a key that I also added "TEST TEST" to.
Which version of JHipster?
jhipsterVersion "6.7.1"

Answer 1

Found the reason. In EmployeeResource, the updateEmployee was calling a version of createEntityUpdateAlert that just sends a message, not a key.
return ResponseEntity.ok()
.headers(HeaderUtil.createEntityUpdateAlert(ENTITY_NAME, employee.getId().toString()))
.body(result);
Obviously, client side only expected a key and threw an error..
I need to change that to the version that sends a key.
return ResponseEntity.ok()
.headers(HeaderUtil.createEntityUpdateAlert(applicationName, true, ENTITY_NAME, employee.getId().toString()))
.body(result);