@ionic/angular 9.0.4-dev.11789491273.11ab1c95 → 9.0.4-dev.11789496656.1690cf55

package/dist/common/utils/boolean-attribute.d.ts

@@ -0,0 +1,24 @@
+/**
+ * Transforms a value to a boolean so that boolean properties can be set by attribute presence,
+ * e.g. `<ion-modal handle>` instead of `<ion-modal [handle]="true">`.
+ *
+ * Strings are coerced the same way Angular's `booleanAttribute` coerces them, so `''` (a bare
+ * attribute) becomes `true` and `'false'` becomes `false`.
+ *
+ * Unlike Angular's `booleanAttribute`, `null` and `undefined` are passed through rather than
+ * coerced to `false`. Components frequently treat them as a state distinct from `false`, and both
+ * reach inputs routinely from the `async` pipe before its first emission and from form control
+ * values:
+ *
+ * ```tsx
+ * // `undefined` means "decide based on the mode", which is not the same as `false`
+ * const showDetail = detail !== undefined ? detail : mode === 'ios';
+ *
+ * // a strict comparison also behaves differently for `null` than it does for `false`
+ * const showHandle = handle !== false;
+ * ```
+ *
+ * Declared as a function rather than an arrow constant because Angular has to resolve input
+ * transforms statically when compiling a library in partial compilation mode.
+ */
+export declare function nullableBooleanAttribute(value: boolean | string | null | undefined): boolean | null | undefined;

package/dist/common/utils/boolean-attribute.js

@@ -0,0 +1,36 @@
+/*
+ * Duplicates `angular-component-lib/boolean-attribute.ts`, which the output
+ * target copies next to each generated proxies file and so is not reachable
+ * from here. `proxy.ts` duplicates `ProxyCmp` for the same reason. Refer to
+ * the TODO at the top of `proxy.ts`.
+ */
+/**
+ * Transforms a value to a boolean so that boolean properties can be set by attribute presence,
+ * e.g. `<ion-modal handle>` instead of `<ion-modal [handle]="true">`.
+ *
+ * Strings are coerced the same way Angular's `booleanAttribute` coerces them, so `''` (a bare
+ * attribute) becomes `true` and `'false'` becomes `false`.
+ *
+ * Unlike Angular's `booleanAttribute`, `null` and `undefined` are passed through rather than
+ * coerced to `false`. Components frequently treat them as a state distinct from `false`, and both
+ * reach inputs routinely from the `async` pipe before its first emission and from form control
+ * values:
+ *
+ * ```tsx
+ * // `undefined` means "decide based on the mode", which is not the same as `false`
+ * const showDetail = detail !== undefined ? detail : mode === 'ios';
+ *
+ * // a strict comparison also behaves differently for `null` than it does for `false`
+ * const showHandle = handle !== false;
+ * ```
+ *
+ * Declared as a function rather than an arrow constant because Angular has to resolve input
+ * transforms statically when compiling a library in partial compilation mode.
+ */
+export function nullableBooleanAttribute(value) {
+    if (value === null || value === undefined) {
+        return value;
+    }
+    return typeof value === 'boolean' ? value : value !== 'false';
+}
+//# sourceMappingURL=boolean-attribute.js.map

package/dist/common/utils/boolean-attribute.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"boolean-attribute.js","sourceRoot":"","sources":["../../../src/common/utils/boolean-attribute.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,UAAU,wBAAwB,CAAC,KAA0C;IACjF,IAAI,KAAK,KAAK,IAAI,IAAI,KAAK,KAAK,SAAS,EAAE,CAAC;QAC1C,OAAO,KAAK,CAAC;IACf,CAAC;IACD,OAAO,OAAO,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,KAAK,KAAK,OAAO,CAAC;AAChE,CAAC","sourcesContent":["/*\n * Duplicates `angular-component-lib/boolean-attribute.ts`, which the output\n * target copies next to each generated proxies file and so is not reachable\n * from here. `proxy.ts` duplicates `ProxyCmp` for the same reason. Refer to\n * the TODO at the top of `proxy.ts`.\n */\n\n/**\n * Transforms a value to a boolean so that boolean properties can be set by attribute presence,\n * e.g. `<ion-modal handle>` instead of `<ion-modal [handle]=\"true\">`.\n *\n * Strings are coerced the same way Angular's `booleanAttribute` coerces them, so `''` (a bare\n * attribute) becomes `true` and `'false'` becomes `false`.\n *\n * Unlike Angular's `booleanAttribute`, `null` and `undefined` are passed through rather than\n * coerced to `false`. Components frequently treat them as a state distinct from `false`, and both\n * reach inputs routinely from the `async` pipe before its first emission and from form control\n * values:\n *\n * ```tsx\n * // `undefined` means \"decide based on the mode\", which is not the same as `false`\n * const showDetail = detail !== undefined ? detail : mode === 'ios';\n *\n * // a strict comparison also behaves differently for `null` than it does for `false`\n * const showHandle = handle !== false;\n * ```\n *\n * Declared as a function rather than an arrow constant because Angular has to resolve input\n * transforms statically when compiling a library in partial compilation mode.\n */\nexport function nullableBooleanAttribute(value: boolean | string | null | undefined): boolean | null | undefined {\n  if (value === null || value === undefined) {\n    return value;\n  }\n  return typeof value === 'boolean' ? value : value !== 'false';\n}\n"]}

package/dist/lazy/directives/angular-component-lib/boolean-attribute.d.ts

@@ -0,0 +1,35 @@
+/**
+ * Transforms a value to a boolean so that boolean properties can be set by attribute presence,
+ * e.g. `<my-component disabled>` instead of `<my-component [disabled]="true">`.
+ *
+ * Strings are coerced the same way Angular's `booleanAttribute` coerces them, so `''` (a bare
+ * attribute) becomes `true` and `'false'` becomes `false`.
+ *
+ * Unlike Angular's `booleanAttribute`, `null` and `undefined` are passed through rather than
+ * coerced to `false`. Components frequently treat them as a state distinct from `false`:
+ *
+ * ```tsx
+ * // `undefined` means "decide based on the mode", which is not the same as `false`
+ * const showDetail = detail !== undefined ? detail : mode === 'ios';
+ *
+ * // a strict comparison also behaves differently for `null` than it does for `false`
+ * const showHandle = handle !== false;
+ * ```
+ *
+ * Both values reach inputs routinely in Angular templates, from the `async` pipe before its
+ * first emission and from form control values, so coercing them would change the behavior of
+ * bindings that work today.
+ *
+ * This is implemented here rather than imported from `@angular/core` so that consumers on
+ * Angular versions without `booleanAttribute` are unaffected by this file being generated.
+ *
+ * The parameter type is what Angular derives `ngAcceptInputType_*` from, so it decides which
+ * template bindings compile. Widening it to `unknown` would let any expression through.
+ *
+ * Declared as a function rather than an arrow constant because Angular has to resolve input
+ * transforms statically when compiling a library in partial compilation mode.
+ *
+ * This lives in its own file, separate from `utils.ts`, so that it carries no runtime imports.
+ * That keeps it independently type-checkable without pulling `rxjs` in for `proxyOutputs`.
+ */
+export declare function nullableBooleanAttribute(value: boolean | string | null | undefined): boolean | null | undefined;

package/dist/lazy/directives/angular-component-lib/boolean-attribute.js

@@ -0,0 +1,43 @@
+/* eslint-disable */
+/* tslint:disable */
+/**
+ * Transforms a value to a boolean so that boolean properties can be set by attribute presence,
+ * e.g. `<my-component disabled>` instead of `<my-component [disabled]="true">`.
+ *
+ * Strings are coerced the same way Angular's `booleanAttribute` coerces them, so `''` (a bare
+ * attribute) becomes `true` and `'false'` becomes `false`.
+ *
+ * Unlike Angular's `booleanAttribute`, `null` and `undefined` are passed through rather than
+ * coerced to `false`. Components frequently treat them as a state distinct from `false`:
+ *
+ * ```tsx
+ * // `undefined` means "decide based on the mode", which is not the same as `false`
+ * const showDetail = detail !== undefined ? detail : mode === 'ios';
+ *
+ * // a strict comparison also behaves differently for `null` than it does for `false`
+ * const showHandle = handle !== false;
+ * ```
+ *
+ * Both values reach inputs routinely in Angular templates, from the `async` pipe before its
+ * first emission and from form control values, so coercing them would change the behavior of
+ * bindings that work today.
+ *
+ * This is implemented here rather than imported from `@angular/core` so that consumers on
+ * Angular versions without `booleanAttribute` are unaffected by this file being generated.
+ *
+ * The parameter type is what Angular derives `ngAcceptInputType_*` from, so it decides which
+ * template bindings compile. Widening it to `unknown` would let any expression through.
+ *
+ * Declared as a function rather than an arrow constant because Angular has to resolve input
+ * transforms statically when compiling a library in partial compilation mode.
+ *
+ * This lives in its own file, separate from `utils.ts`, so that it carries no runtime imports.
+ * That keeps it independently type-checkable without pulling `rxjs` in for `proxyOutputs`.
+ */
+export function nullableBooleanAttribute(value) {
+    if (value === null || value === undefined) {
+        return value;
+    }
+    return typeof value === 'boolean' ? value : value !== 'false';
+}
+//# sourceMappingURL=boolean-attribute.js.map

package/dist/lazy/directives/angular-component-lib/boolean-attribute.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"boolean-attribute.js","sourceRoot":"","sources":["../../../../src/lazy/directives/angular-component-lib/boolean-attribute.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,oBAAoB;AAEpB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiCG;AACH,MAAM,UAAU,wBAAwB,CAAC,KAA0C;IACjF,IAAI,KAAK,KAAK,IAAI,IAAI,KAAK,KAAK,SAAS,EAAE,CAAC;QAC1C,OAAO,KAAK,CAAC;IACf,CAAC;IACD,OAAO,OAAO,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,KAAK,KAAK,OAAO,CAAC;AAChE,CAAC","sourcesContent":["/* eslint-disable */\n/* tslint:disable */\n\n/**\n * Transforms a value to a boolean so that boolean properties can be set by attribute presence,\n * e.g. `<my-component disabled>` instead of `<my-component [disabled]=\"true\">`.\n *\n * Strings are coerced the same way Angular's `booleanAttribute` coerces them, so `''` (a bare\n * attribute) becomes `true` and `'false'` becomes `false`.\n *\n * Unlike Angular's `booleanAttribute`, `null` and `undefined` are passed through rather than\n * coerced to `false`. Components frequently treat them as a state distinct from `false`:\n *\n * ```tsx\n * // `undefined` means \"decide based on the mode\", which is not the same as `false`\n * const showDetail = detail !== undefined ? detail : mode === 'ios';\n *\n * // a strict comparison also behaves differently for `null` than it does for `false`\n * const showHandle = handle !== false;\n * ```\n *\n * Both values reach inputs routinely in Angular templates, from the `async` pipe before its\n * first emission and from form control values, so coercing them would change the behavior of\n * bindings that work today.\n *\n * This is implemented here rather than imported from `@angular/core` so that consumers on\n * Angular versions without `booleanAttribute` are unaffected by this file being generated.\n *\n * The parameter type is what Angular derives `ngAcceptInputType_*` from, so it decides which\n * template bindings compile. Widening it to `unknown` would let any expression through.\n *\n * Declared as a function rather than an arrow constant because Angular has to resolve input\n * transforms statically when compiling a library in partial compilation mode.\n *\n * This lives in its own file, separate from `utils.ts`, so that it carries no runtime imports.\n * That keeps it independently type-checkable without pulling `rxjs` in for `proxyOutputs`.\n */\nexport function nullableBooleanAttribute(value: boolean | string | null | undefined): boolean | null | undefined {\n  if (value === null || value === undefined) {\n    return value;\n  }\n  return typeof value === 'boolean' ? value : value !== 'false';\n}\n"]}