angular.js/lib/grunt, branch v1.2.0 chore(Grunt): use the latest Content-Security-Policy header in csp mode 2013-10-22T22:21:24+00:00 Igor Minar 2013-10-22T22:05:40+00:00 2d8d6dd192322a60a3dbad7485d1395a161b3130 






fix: don't inline css in csp mode.
2013-10-22T22:21:23+00:00

tigbro

2013-10-14T19:06:26+00:00

a86cf20e67202d614bbcaf038c5e04db94483256

Also add `angular-csp.css` to the resulting build.





Also add `angular-csp.css` to the resulting build.







fix(csp): fix csp auto-detection and stylesheet injection
2013-10-19T00:33:53+00:00

Igor Minar

2013-10-15T22:00:22+00:00

08f376f2ea3d3bb384f10e3c01f7d48ed21ce351

When we refactored , we broke the csp mode because the previous implementation
relied on the fact that it was ok to lazy initialize the .csp property, this
is not the case any more.

Besides, we need to know about csp mode during bootstrap and avoid injecting the
stylesheet when csp is active, so I refactored the code to fix both issues.

PR #4411 will follow up on this commit and add more improvements.

Closes #917
Closes #2963
Closes #4394
Closes #4444

BREAKING CHANGE: triggering ngCsp directive via `ng:csp` attribute is not
supported any more. Please use data-ng-csp instead.





When we refactored , we broke the csp mode because the previous implementation
relied on the fact that it was ok to lazy initialize the .csp property, this
is not the case any more.

Besides, we need to know about csp mode during bootstrap and avoid injecting the
stylesheet when csp is active, so I refactored the code to fix both issues.

PR #4411 will follow up on this commit and add more improvements.

Closes #917
Closes #2963
Closes #4394
Closes #4444

BREAKING CHANGE: triggering ngCsp directive via `ng:csp` attribute is not
supported any more. Please use data-ng-csp instead.







chore(grunt): switch to the new //# sourceMappingURL pragma
2013-10-01T19:30:50+00:00

Michał Gołębiowski

2013-09-24T17:52:20+00:00

936101041a9a1f1cf9fecf6b5fcfae206cd15424

All browsers except from Chrome implemented both the old
"//@ sourceMappingURL" and the new "//# sourceMappingURL" pragmas
in the same version so the only reason to keep the old one was Chrome.
However, Chrome 29, i.e. current stable version already supports
the new pragma so there's no need to wait any longer.





All browsers except from Chrome implemented both the old
"//@ sourceMappingURL" and the new "//# sourceMappingURL" pragmas
in the same version so the only reason to keep the old one was Chrome.
However, Chrome 29, i.e. current stable version already supports
the new pragma so there's no need to wait any longer.







chore(grunt): support semver v2 version number format
2013-09-04T12:50:39+00:00

Igor Minar

2013-09-04T12:28:14+00:00

7b203fcff6dd01da0bebb43130a0e861c05c4e9c

previously we couldn't use it because of bower bugs





previously we couldn't use it because of bower bugs







chore(travis): use ports proxied by SauceLabs
2013-08-28T22:46:19+00:00

Vojta Jina

2013-08-28T18:55:14+00:00

df17a2c7495cea22f803d1e2e22329712a7fd25a

Some browser does not allow to proxy localhost and so SL uses another proxy on the VM. This proxy only proxies some ports (SauceConnect proxies all ports).

This is the issue why Safari didn't connect for e2e tests, because 9877 was not proxied.

This change makes sure we use SL enabled ports.





Some browser does not allow to proxy localhost and so SL uses another proxy on the VM. This proxy only proxies some ports (SauceConnect proxies all ports).

This is the issue why Safari didn't connect for e2e tests, because 9877 was not proxied.

This change makes sure we use SL enabled ports.







chore: run more browsers on Travis (IE8,IE9,IE10,Safari,FF)
2013-08-23T23:49:10+00:00

Vojta Jina

2013-08-20T21:43:15+00:00

7909ebedc2a098f041dd2d3835e7297392bfdb7d

Also instead of running everything in parallel, there are only two parallel tasks:
- e2e tests running in the background (only on Chrome)
- all the unit tests running sequentially





Also instead of running everything in parallel, there are only two parallel tasks:
- e2e tests running in the background (only on Chrome)
- all the unit tests running sequentially







fix(grunt): fix regex in grunt util to handle pre-release versions
2013-08-15T19:41:14+00:00

Brian Ford

2013-08-13T20:17:09+00:00

fe267e30b95e8f48ddc670b97d485f18fb64d39e

NOTE: this also includes a temporary work-around for Bower





NOTE: this also includes a temporary work-around for Bower







chore(ngdocs): fixup the docs version switcher
2013-08-14T19:02:44+00:00

Igor Minar

2013-08-13T23:57:52+00:00

7215afa21c91c33c924a5aba7f3a704983642897












chore: disable npm install on Travis
2013-08-14T06:02:21+00:00

Vojta Jina

2013-08-13T22:14:55+00:00

c63fbbbcd1147c7e55c3e1d4118bd3a5f6059810

Grunt is configured to run `npm install` before every task. That is convenient when switching a branch for example.

On Travis, this makes no sense and is causing tons of NPM warnings (eg. packages not defining repository field etc).





Grunt is configured to run `npm install` before every task. That is convenient when switching a branch for example.

On Travis, this makes no sense and is causing tons of NPM warnings (eg. packages not defining repository field etc).