@angular-wave/angular.ts 0.0.46 → 0.0.47

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@angular-wave/angular.ts",
   "license": "MIT",
-  "version": "0.0.46",
+  "version": "0.0.47",
   "type": "module",
   "main": "dist/angular-ts.esm.js",
   "browser": "dist/angular-ts.umd.js",

package/src/animations/animate-css-driver.js

@@ -137,7 +137,7 @@ export const $$AnimateCssDriverProvider = [
 
             // we iterate directly since safari messes up and doesn't return
             // all the keys for the coords object when iterated
-            forEach(["width", "height", "top", "left"], (key) => {
+            ["width", "height", "top", "left"].forEach((key) => {
               let value = coords[key];
               switch (key) {
                 case "top":

package/src/animations/animate-queue.js

@@ -54,7 +54,7 @@ export const $$AnimateQueueProvider = [
       const keys = classString.split(ONE_SPACE);
       const map = Object.create(null);
 
-      forEach(keys, (key) => {
+      keys.forEach((key) => {
         map[key] = true;
       });
       return map;
@@ -256,7 +256,7 @@ export const $$AnimateQueueProvider = [
           const matches = [];
           const entries = callbackRegistry[event];
           if (entries) {
-            forEach(entries, (entry) => {
+            entries.forEach((entry) => {
               if (contains.call(entry.node, targetNode)) {
                 matches.push(entry.callback);
               } else if (
@@ -694,7 +694,7 @@ export const $$AnimateQueueProvider = [
             runInNextPostDigestOrNow(() => {
               const callbacks = findCallbacks(parentNode, node, event);
               if (callbacks.length) {
-                forEach(callbacks, (callback) => {
+                callbacks.forEach((callback) => {
                   callback(element, phase, data);
                 });
                 cleanupEventListeners(phase, node);

package/src/core/filter/filter.js

@@ -1,4 +1,4 @@
-import { forEach, isObject } from "../../shared/utils";
+import { isObject } from "../../shared/utils";
 import { filterFilter } from "../../filters/filter";
 import { jsonFilter } from "../../filters/filters";
 import { limitToFilter } from "../../filters/limit-to";
@@ -11,7 +11,7 @@ export function $FilterProvider($provide) {
   function register(name, factory) {
     if (isObject(name)) {
       const filters = {};
-      forEach(name, (filter, key) => {
+      Object.entries(name).forEach(([key, filter]) => {
         filters[key] = register(key, filter);
       });
       return filters;

package/src/core/location/location.js

@@ -583,7 +583,7 @@ const locationPrototype = {
         } else if (isObject(search)) {
           search = structuredClone(search, {});
           // remove object undefined or null properties
-          forEach(search, (value, key) => {
+          Object.entries(search).forEach(([key, value]) => {
             if (value == null) delete search[key];
           });
 

package/src/core/parser/parse.js

@@ -778,7 +778,7 @@ function findConstantAndWatchExpressions(ast, $filter, parentIsPure) {
   switch (ast.type) {
     case ASTType.Program:
       allConstants = true;
-      forEach(ast.body, (expr) => {
+      /** @type {[any]} */ (ast.body).forEach((expr) => {
         findConstantAndWatchExpressions(expr.expression, $filter, astIsPure);
         allConstants = allConstants && expr.expression.constant;
       });

package/src/directive/attrs/attrs.js

@@ -1,194 +1,13 @@
 import { BOOLEAN_ATTR } from "../../shared/jqlite/jqlite";
-import { forEach, directiveNormalize } from "../../shared/utils";
+import { directiveNormalize } from "../../shared/utils";
 import { ALIASED_ATTR } from "../../shared/constants";
 
-/**
- * @ngdoc directive
- * @name ngHref
- * @restrict A
- * @priority 99
- *
- * @description
- * Using AngularJS markup like `{{hash}}` in an href attribute will
- * make the link go to the wrong URL if the user clicks it before
- * AngularJS has a chance to replace the `{{hash}}` markup with its
- * value. Until AngularJS replaces the markup the link will be broken
- * and will most likely return a 404 error. The `ngHref` directive
- * solves this problem.
- *
- * The wrong way to write it:
- * ```html
- * <a href="http://www.gravatar.com/avatar/{{hash}}">link1</a>
- * ```
- *
- * The correct way to write it:
- * ```html
- * <a ng-href="http://www.gravatar.com/avatar/{{hash}}">link1</a>
- * ```
- *
- * @element A
- * @param {template} ngHref any string which can contain `{{}}` markup.
- *
- */
-
 export const REGEX_STRING_REGEXP = /^\/(.+)\/([a-z]*)$/;
-/**
- * @ngdoc directive
- * @name ngSrc
- * @restrict A
- * @priority 99
- *
- * @description
- * Using AngularJS markup like `{{hash}}` in a `src` attribute doesn't
- * work right: The browser will fetch from the URL with the literal
- * text `{{hash}}` until AngularJS replaces the expression inside
- * `{{hash}}`. The `ngSrc` directive solves this problem.
- *
- * The buggy way to write it:
- * ```html
- * <img src="http://www.gravatar.com/avatar/{{hash}}" alt="Description"/>
- * ```
- *
- * The correct way to write it:
- * ```html
- * <img ng-src="http://www.gravatar.com/avatar/{{hash}}" alt="Description" />
- * ```
- *
- * @element IMG
- * @param {template} ngSrc any string which can contain `{{}}` markup.
- */
-
-/**
- * @ngdoc directive
- * @name ngSrcset
- * @restrict A
- * @priority 99
- *
- * @description
- * Using AngularJS markup like `{{hash}}` in a `srcset` attribute doesn't
- * work right: The browser will fetch from the URL with the literal
- * text `{{hash}}` until AngularJS replaces the expression inside
- * `{{hash}}`. The `ngSrcset` directive solves this problem.
- *
- * The buggy way to write it:
- * ```html
- * <img srcset="http://www.gravatar.com/avatar/{{hash}} 2x" alt="Description"/>
- * ```
- *
- * The correct way to write it:
- * ```html
- * <img ng-srcset="http://www.gravatar.com/avatar/{{hash}} 2x" alt="Description" />
- * ```
- *
- * @element IMG
- * @param {template} ngSrcset any string which can contain `{{}}` markup.
- */
-
-/**
- * @ngdoc directive
- * @name ngDisabled
- * @restrict A
- * @priority 100
- *
- * @description
- *
- * This directive sets the `disabled` attribute on the element (typically a form control,
- * e.g. `input`, `button`, `select` etc.) if the
- * {@link guide/expression expression} inside `ngDisabled` evaluates to truthy.
- *
- * A special directive is necessary because we cannot use interpolation inside the `disabled`
- * attribute. See the {@link guide/interpolation interpolation guide} for more info.
- *
- * @param {string} ngDisabled If the {@link guide/expression expression} is truthy,
- *     then the `disabled` attribute will be set on the element
- */
-
-/**
- * @ngdoc directive
- * @name ngChecked
- * @restrict A
- * @priority 100
- *
- * @description
- * Sets the `checked` attribute on the element, if the expression inside `ngChecked` is truthy.
- *
- * Note that this directive should not be used together with {@link ngModel `ngModel`},
- * as this can lead to unexpected behavior.
- *
- * A special directive is necessary because we cannot use interpolation inside the `checked`
- * attribute. See the {@link guide/interpolation interpolation guide} for more info.
- *
- * @element INPUT
- * @param {string} ngChecked If the {@link guide/expression expression} is truthy,
- *     then the `checked` attribute will be set on the element
- */
-
-/**
- *
- * @description
- *
- * Sets the `readonly` attribute on the element, if the expression inside `ngReadonly` is truthy.
- * Note that `readonly` applies only to `input` elements with specific types. [See the input docs on
- * MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly) for more information.
- *
- * A special directive is necessary because we cannot use interpolation inside the `readonly`
- * attribute. See the {@link guide/interpolation interpolation guide} for more info.
- * @element INPUT
- * @param {string} ngReadonly If the {@link guide/expression expression} is truthy,
- *     then special attribute "readonly" will be set on the element
- */
-
-/**
- * @ngdoc directive
- * @name ngSelected
- * @restrict A
- * @priority 100
- *
- * @description
- *
- * Sets the `selected` attribute on the element, if the expression inside `ngSelected` is truthy.
- *
- * A special directive is necessary because we cannot use interpolation inside the `selected`
- * attribute. See the {@link guide/interpolation interpolation guide} for more info.
- *
- * <div class="alert alert-warning">
- *   **Note:** `ngSelected` does not interact with the `select` and `ngModel` directives, it only
- *   sets the `selected` attribute on the element. If you are using `ngModel` on the select, you
- *   should not use `ngSelected` on the options, as `ngModel` will set the select value and
- *   selected options.
- * </div>
- * @element OPTION
- * @param {string} ngSelected If the {@link guide/expression expression} is truthy,
- *     then special attribute "selected" will be set on the element
- */
-
-/**
- * @ngdoc directive
- * @name ngOpen
- * @restrict A
- * @priority 100
- *
- * @description
- *
- * Sets the `open` attribute on the element, if the expression inside `ngOpen` is truthy.
- *
- * A special directive is necessary because we cannot use interpolation inside the `open`
- * attribute. See the {@link guide/interpolation interpolation guide} for more info.
- *
- * ## A note about browser compatibility
- *
- * Internet Explorer and Edge do not support the `details` element, it is
- * recommended to use {@link ng.ngShow} and {@link ng.ngHide} instead.
- *
- * @element DETAILS
- * @param {string} ngOpen If the {@link guide/expression expression} is truthy,
- *     then special attribute "open" will be set on the element
- */
 
 export const ngAttributeAliasDirectives = {};
 
 // boolean attrs are evaluated
-forEach(BOOLEAN_ATTR, (propName, attrName) => {
+Object.entries(BOOLEAN_ATTR).forEach(([attrName, propName]) => {
   // binding to multiple is not supported
   if (propName === "multiple") return;
 
@@ -220,7 +39,7 @@ forEach(BOOLEAN_ATTR, (propName, attrName) => {
 });
 
 // aliased input attrs are evaluated
-forEach(ALIASED_ATTR, (htmlAttr, ngAttr) => {
+Object.entries(ALIASED_ATTR).forEach(([ngAttr]) => {
   ngAttributeAliasDirectives[ngAttr] = function () {
     return {
       priority: 100,
@@ -244,7 +63,7 @@ forEach(ALIASED_ATTR, (htmlAttr, ngAttr) => {
 });
 
 // ng-src, ng-srcset, ng-href are interpolated
-forEach(["src", "srcset", "href"], (attrName) => {
+["src", "srcset", "href"].forEach((attrName) => {
   const normalized = directiveNormalize(`ng-${attrName}`);
   ngAttributeAliasDirectives[normalized] = [
     "$sce",

package/src/directive/attrs/attrs.md

@@ -0,0 +1,224 @@
+/\*\*
+
+- @ngdoc directive
+- @name ngHref
+- @restrict A
+- @priority 99
+-
+- @description
+- Using AngularJS markup like `{{hash}}` in an href attribute will
+- make the link go to the wrong URL if the user clicks it before
+- AngularJS has a chance to replace the `{{hash}}` markup with its
+- value. Until AngularJS replaces the markup the link will be broken
+- and will most likely return a 404 error. The `ngHref` directive
+- solves this problem.
+-
+- The wrong way to write it:
+- ```html
+
+  ```
+
+- <a href="http://www.gravatar.com/avatar/{{hash}}">link1</a>
+- ```
+
+  ```
+
+-
+- The correct way to write it:
+- ```html
+
+  ```
+
+- <a ng-href="http://www.gravatar.com/avatar/{{hash}}">link1</a>
+- ```
+
+  ```
+
+-
+- @element A
+- @param {template} ngHref any string which can contain `{{}}` markup.
+- \*/
+
+/\*\*
+
+- @ngdoc directive
+- @name ngSrc
+- @restrict A
+- @priority 99
+-
+- @description
+- Using AngularJS markup like `{{hash}}` in a `src` attribute doesn't
+- work right: The browser will fetch from the URL with the literal
+- text `{{hash}}` until AngularJS replaces the expression inside
+- `{{hash}}`. The `ngSrc` directive solves this problem.
+-
+- The buggy way to write it:
+- ```html
+
+  ```
+
+- <img src="http://www.gravatar.com/avatar/{{hash}}" alt="Description"/>
+- ```
+
+  ```
+
+-
+- The correct way to write it:
+- ```html
+
+  ```
+
+- <img ng-src="http://www.gravatar.com/avatar/{{hash}}" alt="Description" />
+- ```
+
+  ```
+
+-
+- @element IMG
+- @param {template} ngSrc any string which can contain `{{}}` markup.
+  \*/
+
+/\*\*
+
+- @ngdoc directive
+- @name ngSrcset
+- @restrict A
+- @priority 99
+-
+- @description
+- Using AngularJS markup like `{{hash}}` in a `srcset` attribute doesn't
+- work right: The browser will fetch from the URL with the literal
+- text `{{hash}}` until AngularJS replaces the expression inside
+- `{{hash}}`. The `ngSrcset` directive solves this problem.
+-
+- The buggy way to write it:
+- ```html
+
+  ```
+
+- <img srcset="http://www.gravatar.com/avatar/{{hash}} 2x" alt="Description"/>
+- ```
+
+  ```
+
+-
+- The correct way to write it:
+- ```html
+
+  ```
+
+- <img ng-srcset="http://www.gravatar.com/avatar/{{hash}} 2x" alt="Description" />
+- ```
+
+  ```
+
+-
+- @element IMG
+- @param {template} ngSrcset any string which can contain `{{}}` markup.
+  \*/
+
+/\*\*
+
+- @ngdoc directive
+- @name ngDisabled
+- @restrict A
+- @priority 100
+-
+- @description
+-
+- This directive sets the `disabled` attribute on the element (typically a form control,
+- e.g. `input`, `button`, `select` etc.) if the
+- {@link guide/expression expression} inside `ngDisabled` evaluates to truthy.
+-
+- A special directive is necessary because we cannot use interpolation inside the `disabled`
+- attribute. See the {@link guide/interpolation interpolation guide} for more info.
+-
+- @param {string} ngDisabled If the {@link guide/expression expression} is truthy,
+-     then the `disabled` attribute will be set on the element
+  \*/
+
+/\*\*
+
+- @ngdoc directive
+- @name ngChecked
+- @restrict A
+- @priority 100
+-
+- @description
+- Sets the `checked` attribute on the element, if the expression inside `ngChecked` is truthy.
+-
+- Note that this directive should not be used together with {@link ngModel `ngModel`},
+- as this can lead to unexpected behavior.
+-
+- A special directive is necessary because we cannot use interpolation inside the `checked`
+- attribute. See the {@link guide/interpolation interpolation guide} for more info.
+-
+- @element INPUT
+- @param {string} ngChecked If the {@link guide/expression expression} is truthy,
+-     then the `checked` attribute will be set on the element
+  \*/
+
+/\*\*
+
+-
+- @description
+-
+- Sets the `readonly` attribute on the element, if the expression inside `ngReadonly` is truthy.
+- Note that `readonly` applies only to `input` elements with specific types. [See the input docs on
+- MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly) for more information.
+-
+- A special directive is necessary because we cannot use interpolation inside the `readonly`
+- attribute. See the {@link guide/interpolation interpolation guide} for more info.
+- @element INPUT
+- @param {string} ngReadonly If the {@link guide/expression expression} is truthy,
+-     then special attribute "readonly" will be set on the element
+  \*/
+
+/\*\*
+
+- @ngdoc directive
+- @name ngSelected
+- @restrict A
+- @priority 100
+-
+- @description
+-
+- Sets the `selected` attribute on the element, if the expression inside `ngSelected` is truthy.
+-
+- A special directive is necessary because we cannot use interpolation inside the `selected`
+- attribute. See the {@link guide/interpolation interpolation guide} for more info.
+-
+- <div class="alert alert-warning">
+- **Note:** `ngSelected` does not interact with the `select` and `ngModel` directives, it only
+- sets the `selected` attribute on the element. If you are using `ngModel` on the select, you
+- should not use `ngSelected` on the options, as `ngModel` will set the select value and
+- selected options.
+- </div>
+- @element OPTION
+- @param {string} ngSelected If the {@link guide/expression expression} is truthy,
+-     then special attribute "selected" will be set on the element
+  \*/
+
+/\*\*
+
+- @ngdoc directive
+- @name ngOpen
+- @restrict A
+- @priority 100
+-
+- @description
+-
+- Sets the `open` attribute on the element, if the expression inside `ngOpen` is truthy.
+-
+- A special directive is necessary because we cannot use interpolation inside the `open`
+- attribute. See the {@link guide/interpolation interpolation guide} for more info.
+-
+- ## A note about browser compatibility
+-
+- Internet Explorer and Edge do not support the `details` element, it is
+- recommended to use {@link ng.ngShow} and {@link ng.ngHide} instead.
+-
+- @element DETAILS
+- @param {string} ngOpen If the {@link guide/expression expression} is truthy,
+-     then special attribute "open" will be set on the element
+  \*/