Earlier, AYTF is adding additional CC when returning unformatted result - for cases where the input digits are dropped for formatting. Eg: MX case: "+5213314010666" => "+52 +5213314010666". b/183053929
Now we. are proactively ensuring that no formatting is applied, where a format is chosen that would otherwise have led to some digits being dropped.
Why the input digits are dropped:
- In MX, the mobile token (1) is no more used, so when it is present in input, the formatted result should not contain it.
- However when AYTF, we should not be removing the input digits on the fly.
- More details in cl/373115460 and b/183053929
* Make JS util test changes to reflect the annotation updates (like not null parameters). This is followup to recent cl/300367316.
* Add non-nullable modifier to return type of functions never returning null. More details in cl/300838092
* Removing blank line.
* Updates the type annotations in phonenumberutil.js
Updates the type annotations to indicate the inputs are required to be non-null.
* Update pending_code_changes.txt
* Update pending_code_changes.txt
Compiling errors found when compiled against new version of closure-compiler
>> No warning class for name: ambiguousFunctionDecl
>> Same case for:
fileoverviewTags google/closure-compiler@04cba67
internetExplorerChecks google/closure-compiler@baab835
>> Moreover, deprecated syntax errors for defineClass
"[exec] /Users/lee/ClickToCloud/git/closure-library/closure/goog/base.js:2259: ERROR - [JSC_DEPRECATED_PROP_REASON]"
So we have updated the build.xml so that it no more considers these specific issues as errors and block the build/compilation.