Consider refactoring how we react to missing entities while localizing document

RESOLVED INCOMPLETE

Status

L20n
HTML Bindings
RESOLVED INCOMPLETE
5 years ago
3 years ago

People

(Reporter: gandalf, Unassigned)

Tracking

({APIchange})

unspecified
Next
x86
Mac OS X
APIchange
Bug Flags:
blocking-parkcity +

Details

(Reporter)

Description

5 years ago
An idea from bug 801663 is to change how we react to missing entities while localizing the document.

We then adjust l20n-xml code to:
 - switch this flag on on localizationReady when it begins localizing nodes
 - when it encounters a node that is missing (and throws exception) it ignites fallback context loading asynchronously and add this node to the list of nodes that will be localized when fallback context is ready
 - it continues localizing nodes, and if it encounters more nodes that cannot be translated it adds them to that list
 - when subcontext is loaded it localizes those that were waiting
 - it fires DocumentLocalized only when all nodes are localized
 - on firing DocumentLocalized it switches off the dontFallback flag to off

 - if DocumentLocalized has loaded and the developer programmatically asks for an entity that we don't have, we load fallback context synchronously.

 - before DocumentLocalized we encourage to use getAsync or prepare for get throwing
Assignee: nobody → gandalf
Keywords: APIchange
Priority: -- → P1
Target Milestone: --- → 1.0 beta
Assignee: gandalf → nobody
Priority: P1 → --
Target Milestone: 1.0 beta → Next
Flags: blocking-parkcity+
We moved to async-only API in the meantime, so this is no longer relevant.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.