Added JSDoc file annotation with @suppress to make the remaining GCC type warnings go away. There are small inconsistencies between the AS and goog JS type (e.g. in goog, 'string' is not an Object), that we cannot compensate for. Since the AS compiler takes care of the type checking on the AS code, IMHO we need not worry that we cover up any runtime errors with this @suppress.

Signed-off-by: Erik de Bruin <erik@ixsoftware.nl>
Revert "Added JSDoc file annotation with @suppress to make the remaining GCC type warnings go away. There are small inconsistencies between the AS and goog JS type (e.g. in goog, 'string' is not an Object), that we cannot compensate for. Since the AS compiler takes care of the type checking on the AS code, IMHO we need not worry that we cover up any runtime errors with this @suppress."

This reverts commit b3f4b7e9454f8a8d1e241922dc0deffc6d653e06.

Signed-off-by: Erik de Bruin <erik@ixsoftware.nl>
Trying again: added JSDoc file annotation with @suppress to make the remaining GCC type warnings go away. There are small inconsistencies between the AS and goog JS type (e.g. in goog, 'string' is not an Object), that we cannot compensate for. Since the AS compiler takes care of the type checking on the AS code, IMHO we need not worry that we cover up any runtime errors with this @suppress.

Signed-off-by: Erik de Bruin <erik@ixsoftware.nl>
Changed tests with the new file 'header' JSDoc with @suppress {checkTypes}

Signed-off-by: Erik de Bruin <erik@ixsoftware.nl>
Made the default for the --strict-publish argument 'true', so the warning are for all to see, unless switched off with --strict-publish=false. Since we're down to the low tens of warnings, it's worth to keep them showing so we eventually look into making them go away.

Signed-off-by: Erik de Bruin <erik@ixsoftware.nl>