@symbiote-native/angular 3.3.0 → 3.4.0

package/src/modules/animated/index.ts

@@ -6,29 +6,9 @@
 // `Animated.timing(new Animated.Value(0), …).start()`, works against the Angular-driven engine.
 
 import {
-  AnimatedValue,
-  AnimatedValueXY,
-  AnimatedColor,
+  AnimatedDrivers,
   AnimatedMock,
-  Easing,
   Platform,
-  timing,
-  spring,
-  decay,
-  parallel,
-  sequence,
-  stagger,
-  loop,
-  delay,
-  add,
-  subtract,
-  multiply,
-  divide,
-  modulo,
-  diffClamp,
-  event,
-  forkEvent,
-  unforkEvent,
 } from '@symbiote-native/engine';
 import {
   AnimatedFlatList,
@@ -61,37 +41,12 @@ export {
 // components exist. Angular still cannot synthesize arbitrary animated wrappers at runtime; custom
 // animated components remain explicit standalone components over AnimatedComponentBase.
 
-// The live, JS-driven driver namespace (real frames). RN's AnimatedImplementation.
-const liveDrivers = {
-  Value: AnimatedValue,
-  ValueXY: AnimatedValueXY,
-  Color: AnimatedColor,
-  Easing,
-  timing,
-  spring,
-  decay,
-  parallel,
-  sequence,
-  stagger,
-  loop,
-  delay,
-  add,
-  subtract,
-  multiply,
-  divide,
-  modulo,
-  diffClamp,
-  event,
-  forkEvent,
-  unforkEvent,
-};
-
 // RN swaps the WHOLE driver namespace for the mock when the host reports isDisableAnimations
 // (reduced motion / test env): the mock keeps the same surface but jumps each animation to its
 // final value synchronously, no frames. The animated COMPONENTS are live in both branches; only
 // the drivers/value/operators/events half is swapped, exactly like RN spreading `...Animated`
 // (impl or mock) over the same components.
-const drivers = Platform.isDisableAnimations ? AnimatedMock : liveDrivers;
+const drivers = Platform.isDisableAnimations ? AnimatedMock : AnimatedDrivers;
 
 export const Animated = {
   View: AnimatedView,

package/src/modules/app-registry/index.ts

@@ -10,6 +10,7 @@ import type { Type } from '@angular/core';
 import {
   createAppRegistry,
   dlog,
+  HeadlessJsTaskError,
   type IAppParameters,
   type IRunnable,
 } from '@symbiote-native/engine';
@@ -47,8 +48,9 @@ const { AppRegistry, setHostRegistrar } = createAppRegistry<
   IWrapperComponentProvider
 >(runnableFor);
 
-export { AppRegistry, setHostRegistrar };
+export { AppRegistry, HeadlessJsTaskError, setHostRegistrar };
 export type {
+  IAppConfig,
   IAppParameters,
   IRunnable,
   IHostRegistrar,

package/src/modules/status-bar/index.ts

@@ -1,21 +1,20 @@
-// StatusBar, the Angular lifecycle half. The native StatusBarManager driving, the imperative
-// statics, and the Android bar-height constant all live in @symbiote-native/engine, shared verbatim with
-// React and Vue; Metro selects the engine's platform variant. Angular supplies only the
-// declarative shape: a component that renders nothing and re-applies the props through
-// ngOnChanges on mount + every prop change. Imperative statics are attached to the component
-// object the same way RN does.
+// Angular half of StatusBar, the props stack, statics and Android bar-height constant live in
+// @symbiote-native/engine. It renders nothing, keeps one stack entry through `ngOnChanges` and
+// releases it in `ngOnDestroy`
 
 import {
   Component,
   Input,
   type OnChanges,
-  type SimpleChanges,
+  type OnDestroy,
+  type OnInit,
 } from '@angular/core';
 import {
-  applyStatusBarProps,
+  createStatusBarEntry,
   statusBarImperative,
   statusBarCurrentHeight,
   type IColorValue,
+  type IStatusBarAnimation,
   type IStatusBarProps,
   type IStatusBarStyle,
 } from '@symbiote-native/engine';
@@ -27,16 +26,29 @@ export type { IStatusBarProps, IStatusBarStyle } from '@symbiote-native/engine';
   standalone: true,
   template: '',
 })
-class StatusBarComponent implements OnChanges {
+class StatusBarComponent implements OnInit, OnChanges, OnDestroy {
   @Input() barStyle?: IStatusBarStyle;
   @Input() hidden?: boolean;
   @Input() animated?: boolean;
+  @Input() showHideTransition?: IStatusBarAnimation;
   @Input() networkActivityIndicatorVisible?: boolean;
   @Input() backgroundColor?: IColorValue;
   @Input() translucent?: boolean;
 
-  ngOnChanges(_changes: SimpleChanges): void {
-    applyStatusBarProps(this.buildProps());
+  private readonly entry = createStatusBarEntry();
+
+  // `ngOnChanges` never runs without bound inputs, the bar still takes its place in the stack
+  ngOnInit(): void {
+    this.entry.apply(this.buildProps());
+  }
+
+  ngOnChanges(): void {
+    this.entry.apply(this.buildProps());
+  }
+
+  // Popping restores what the stack held below this entry
+  ngOnDestroy(): void {
+    this.entry.release();
   }
 
   private buildProps(): IStatusBarProps {
@@ -44,6 +56,7 @@ class StatusBarComponent implements OnChanges {
       barStyle: this.barStyle,
       hidden: this.hidden,
       animated: this.animated,
+      showHideTransition: this.showHideTransition,
       networkActivityIndicatorVisible: this.networkActivityIndicatorVisible,
       backgroundColor: this.backgroundColor,
       translucent: this.translucent,

package/src/primitives/index.ts

@@ -103,6 +103,13 @@ export class ActivityIndicatorHost extends SymbiotePrimitiveHost {}
 })
 export class SafeAreaViewHost extends SymbiotePrimitiveHost {}
 
+@Component({
+  selector: 'layout-conformance',
+  standalone: true,
+  template: '<ng-content></ng-content>',
+})
+export class LayoutConformanceHost extends SymbiotePrimitiveHost {}
+
 @Component({
   selector: 'modal',
   standalone: true,

package/src/services/color-scheme.service.ts

@@ -11,7 +11,7 @@ import { Appearance, type IColorSchemeName } from '@symbiote-native/engine';
  */
 @Injectable({ providedIn: 'root' })
 export class ColorSchemeService {
-  readonly colorScheme = signal<IColorSchemeName | null>(
+  readonly colorScheme = signal<IColorSchemeName | null | undefined>(
     Appearance.getColorScheme(),
   );