Context Navigation

Changes between Initial Version and Version 2 of Ticket #29853

-              initial
+              v2
 doesn't check the existence of {{{value[1]}}} or {{{value[2]}}} before attempting to access them if {{{value}}} itself is defined. Therefore will return undefined if user attempts to access plural translation, when none is defined.
 - If user provides no translations at all for singular or plural strings it will return formatted un-translated string (Works as expected)
 - If user provides translations for singular and plural strings it will return formatted translated string (Works as expected)
 - If user provides singular translation BUT no plural translation it will return undefined (Unexpected and extremely difficult to debug)
+- If user provides no translations at all for singular or plural strings it will return formatted **un-translated** string (Works as expected)
+- If user provides translations for singular and plural strings it will return formatted **translated** string (Works as expected)
+- If user provides singular translation BUT no plural translation it will return **undefined** (Unexpected and extremely difficult to debug)
 This function should rather fallback to singular translation OR use un-translated plural string in cases where a singular translation is provided but no plural translation is provided.