You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Of course it's better to wrap the contents in IIF. It's even better to fix the problem once and for all - at the source, instead of requiring consumers to repeatedly deal with this problem.
For some reason none of the other Angular deliverables require this "workaround". How about bringing locale in line with the rest of Angular?
This violates a rather clear recommendation of not using global strict mode.
@btford: Since this seems to be such a trivial change (either wrap the contents in an IIFE or move the 'use strict' inside of the config function), is there any reason why Angular wouldn't want something like this (e.g. is it going to create problems elsewhere I don't know about) ?
If nothing else it is good coding style not to have global strict mode, isn't it ?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Strict mode is specified at file level in Angular locale files, e.g. see: angular-locale_aa-dj.js.
This makes them infeasible for concatenation with other scripts that may not be strict mode compliant.
Please remove strict mode from file level there. As far as I see this is a matter of applying some changes to i18n/src/closureI18nExtractor.js
The text was updated successfully, but these errors were encountered: