@angular-wave/angular.ts 0.0.1 → 0.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (70) hide show
  1. package/Makefile +1 -1
  2. package/dist/angular-ts.cjs.js +503 -1686
  3. package/dist/angular-ts.esm.js +503 -1686
  4. package/dist/angular-ts.umd.js +503 -1686
  5. package/package.json +1 -1
  6. package/src/animations/{animateCss.js → animate-css.js} +0 -1
  7. package/src/animations/animation.js +428 -431
  8. package/src/animations/module.js +9 -9
  9. package/src/core/compile.js +4 -1101
  10. package/src/core/compile.md +1192 -0
  11. package/src/core/location.js +1 -1
  12. package/src/core/utils.js +1 -1
  13. package/src/directive/a.js +1 -1
  14. package/src/directive/attrs.js +1 -1
  15. package/src/directive/csp.md +87 -0
  16. package/src/directive/input.js +3 -3
  17. package/src/directive/{ngModel.js → model.js} +1 -1
  18. package/src/directive/select.js +5 -5
  19. package/src/jqLite.js +0 -12
  20. package/src/public.js +24 -24
  21. package/src/services/log.js +66 -116
  22. package/src/services/log.md +39 -0
  23. package/test/jqlite.spec.js +0 -31
  24. package/test/messages/messages.spec.js +1 -1
  25. package/test/ng/compile.spec.js +13 -13
  26. package/test/ng/directive/model-options.spec.js +1 -1
  27. package/test/ng/directive/model.spec.js +1 -1
  28. package/test/ng/directive/options.spec.js +61 -61
  29. package/test/ng/directive/select.spec.js +22 -22
  30. package/test/ng/http-backend.spec.js +1 -1
  31. package/test/ng/on.spec.js +1 -1
  32. package/test/ng/prop.spec.js +54 -62
  33. package/test/ng/sanitize-uri.spec.js +1 -1
  34. package/test/ng/scope.spec.js +1 -1
  35. package/types/jqlite.d.ts +1 -32
  36. package/src/core/attributes.js +0 -199
  37. package/src/directive/ngCsp.js +0 -82
  38. /package/src/animations/{animateCache.js → animate-cache.js} +0 -0
  39. /package/src/animations/{animateChildrenDirective.js → animate-children-directive.js} +0 -0
  40. /package/src/animations/{animateCssDriver.js → animate-css-driver.js} +0 -0
  41. /package/src/animations/{animateJsDriver.js → animate-js-driver.js} +0 -0
  42. /package/src/animations/{animateJs.js → animate-js.js} +0 -0
  43. /package/src/animations/{animateQueue.js → animate-queue.js} +0 -0
  44. /package/src/animations/{ngAnimateSwap.js → animate-swap.js} +0 -0
  45. /package/src/animations/{rafScheduler.js → raf-scheduler.js} +0 -0
  46. /package/src/core/{animateCss.js → animate-css.js} +0 -0
  47. /package/src/core/{animateRunner.js → animate-runner.js} +0 -0
  48. /package/src/core/{exceptionHandler.js → exception-handler.js} +0 -0
  49. /package/src/core/{intervalFactory.js → interval-factory.js} +0 -0
  50. /package/src/core/{rootScope.js → root-scope.js} +0 -0
  51. /package/src/core/{sanitizeUri.js → sanitize-uri.js} +0 -0
  52. /package/src/core/{taskTrackerFactory.js → task-tracker-factory.js} +0 -0
  53. /package/src/directive/{ngClass.js → class.js} +0 -0
  54. /package/src/directive/{ngController.js → controller.js} +0 -0
  55. /package/src/directive/{ngIf.js → if.js} +0 -0
  56. /package/src/directive/{ngInclude.js → include.js} +0 -0
  57. /package/src/directive/{ngModelOptions.js → model-options.js} +0 -0
  58. /package/src/directive/{ngOptions.js → options.js} +0 -0
  59. /package/src/directive/{ngRef.js → ref.js} +0 -0
  60. /package/src/directive/{ngRepeat.js → repeat.js} +0 -0
  61. /package/src/directive/{ngShowHide.js → show-hide.js} +0 -0
  62. /package/src/directive/{ngSwitch.js → switch.js} +0 -0
  63. /package/src/directive/{ngTransclude.js → transclude.js} +0 -0
  64. /package/src/{routeToRegExp.js → route-to-reg-exp.js} +0 -0
  65. /package/src/services/{anchorScroll.js → anchor-scroll.js} +0 -0
  66. /package/src/services/{cacheFactory.js → cache-factory.js} +0 -0
  67. /package/src/services/{cookieReader.js → cookie-reader.js} +0 -0
  68. /package/src/services/{httpBackend.js → http-backend.js} +0 -0
  69. /package/src/services/{templateRequest.js → template-request.js} +0 -0
  70. /package/test/ng/{anomate.spec.js → animate.spec.js} +0 -0
package/src/directive/ngCsp.js DELETED
@@ -1,82 +0,0 @@
1
- /**
2
- * @ngdoc directive
3
- * @name ngCsp
4
- *
5
- * @restrict A
6
- * @element ANY
7
- * @description
8
- *
9
- * AngularJS has some features that can conflict with certain restrictions that are applied when using
10
- * [CSP (Content Security Policy)](https://developer.mozilla.org/en/Security/CSP) rules.
11
- *
12
- * If you intend to implement CSP with these rules then you must tell AngularJS not to use these
13
- * features.
14
- *
15
- * This is necessary when developing things like Google Chrome Extensions or Universal Windows Apps.
16
- *
17
- *
18
- * The following default rules in CSP affect AngularJS:
19
- *
20
- * * The use of `eval()`, `Function(string)` and similar functions to dynamically create and execute
21
- * code from strings is forbidden. AngularJS makes use of this in the {@link $parse} service to
22
- * provide a 30% increase in the speed of evaluating AngularJS expressions. (This CSP rule can be
23
- * disabled with the CSP keyword `unsafe-eval`, but it is generally not recommended as it would
24
- * weaken the protections offered by CSP.)
25
- *
26
- * * The use of inline resources, such as inline `<script>` and `<style>` elements, are forbidden.
27
- * This prevents apps from injecting custom styles directly into the document. AngularJS makes use of
28
- * this to include some CSS rules (e.g. {@link ngCloak} and {@link ngHide}). To make these
29
- * directives work when a CSP rule is blocking inline styles, you must link to the `angular-csp.css`
30
- * in your HTML manually. (This CSP rule can be disabled with the CSP keyword `unsafe-inline`, but
31
- * it is generally not recommended as it would weaken the protections offered by CSP.)
32
- *
33
- * If you do not provide `ngCsp` then AngularJS tries to autodetect if CSP is blocking dynamic code
34
- * creation from strings (e.g., `unsafe-eval` not specified in CSP header) and automatically
35
- * deactivates this feature in the {@link $parse} service. This autodetection, however, triggers a
36
- * CSP error to be logged in the console:
37
- *
38
- * ```
39
- * Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of
40
- * script in the following Content Security Policy directive: "default-src 'self'". Note that
41
- * 'script-src' was not explicitly set, so 'default-src' is used as a fallback.
42
- * ```
43
- *
44
- * This error is harmless but annoying. To prevent the error from showing up, put the `ngCsp`
45
- * directive on an element of the HTML document that appears before the `<script>` tag that loads
46
- * the `angular.js` file.
47
- *
48
- * *Note: This directive is only available in the `ng-csp` and `data-ng-csp` attribute form.*
49
- *
50
- * You can specify which of the CSP related AngularJS features should be deactivated by providing
51
- * a value for the `ng-csp` attribute. The options are as follows:
52
- *
53
- * * no-inline-style: this stops AngularJS from injecting CSS styles into the DOM
54
- *
55
- * * no-unsafe-eval: this stops AngularJS from optimizing $parse with unsafe eval of strings
56
- *
57
- * You can use these values in the following combinations:
58
- *
59
- *
60
- * * No declaration means that AngularJS will assume that you can do inline styles, but it will do
61
- * a runtime check for unsafe-eval. E.g. `<body>`. This is backwardly compatible with previous
62
- * versions of AngularJS.
63
- *
64
- * * A simple `ng-csp` (or `data-ng-csp`) attribute will tell AngularJS to deactivate both inline
65
- * styles and unsafe eval. E.g. `<body ng-csp>`. This is backwardly compatible with previous
66
- * versions of AngularJS.
67
- *
68
- * * Specifying only `no-unsafe-eval` tells AngularJS that we must not use eval, but that we can
69
- * inject inline styles. E.g. `<body ng-csp="no-unsafe-eval">`.
70
- *
71
- * * Specifying only `no-inline-style` tells AngularJS that we must not inject styles, but that we can
72
- * run eval - no automatic check for unsafe eval will occur. E.g. `<body ng-csp="no-inline-style">`
73
- *
74
- * * Specifying both `no-unsafe-eval` and `no-inline-style` tells AngularJS that we must not inject
75
- * styles nor use eval, which is the same as an empty: ng-csp.
76
- * E.g.`<body ng-csp="no-inline-style;no-unsafe-eval">`
77
-
78
- // `ngCsp` is not implemented as a proper directive any more, because we need it be processed while
79
- // we bootstrap the app (before `$parse` is instantiated). For this reason, we just have the `csp()`
80
- // fn that looks for the `ng-csp` attribute anywhere in the current doc.
81
- // TODO MOVE CSP to PARSE CONFIG as this should not even be a directive
82
- */
/package/src/animations/{animateJs.js → animate-js.js} RENAMED
File without changes
/package/src/core/{animateCss.js → animate-css.js} RENAMED
File without changes
/package/src/core/{rootScope.js → root-scope.js} RENAMED
File without changes
/package/src/core/{sanitizeUri.js → sanitize-uri.js} RENAMED
File without changes
/package/src/directive/{ngClass.js → class.js} RENAMED
File without changes
/package/src/directive/{ngIf.js → if.js} RENAMED
File without changes
/package/src/directive/{ngInclude.js → include.js} RENAMED
File without changes
/package/src/directive/{ngOptions.js → options.js} RENAMED
File without changes
/package/src/directive/{ngRef.js → ref.js} RENAMED
File without changes
/package/src/directive/{ngRepeat.js → repeat.js} RENAMED
File without changes
/package/src/directive/{ngShowHide.js → show-hide.js} RENAMED
File without changes
/package/src/directive/{ngSwitch.js → switch.js} RENAMED
File without changes
/package/src/{routeToRegExp.js → route-to-reg-exp.js} RENAMED
File without changes
/package/test/ng/{anomate.spec.js → animate.spec.js} RENAMED
File without changes