(2) If a string key would be exceptionally long, use a key name that is an abbreviated form of the string value, or that captures the purpose/essence of the value.
Inspecting number-play_en.json, these strings do not conform. They should be "hearTotal" and "hearTotalDescription".
"readAloud": {
"value": "Hear Total"
},
"readAloudDescription": {
"value": "Hear the updated total as you interact."
},
It would be easy for me to change these, but I'm not sure if there are existing translations for this sim that would be disturbed (prototype?), or if it's OK to disturb prototype strings. Even if there are prototype translations, I recommend that we still make this change.
From the CRC:
Inspecting number-play_en.json, these strings do not conform. They should be "hearTotal" and "hearTotalDescription".
It would be easy for me to change these, but I'm not sure if there are existing translations for this sim that would be disturbed (prototype?), or if it's OK to disturb prototype strings. Even if there are prototype translations, I recommend that we still make this change.