Logic for missing localization key and tables

[bestwnh]

For the current version(3.0-alpha.8), if the view use some LocalizedKeyString but can't find the value for it, the whole page break with error missingKeys or missingTables.

I thought a string missing should not break the whole page. So I suggest if the localized key is missing for current locale, first use the value for default locale, if still missing fallback to the key value that set in the View. If possible, output the error in the browser console. That can help developer find out the missing translation but also provide a functional page even the developer missing some translation string.

Localization is good, but functional page should be more important.