@applicaster/zapp-react-native-ui-components 15.0.0-rc.98 → 15.1.0-rc.1

package/Components/River/TV/withFocusableGroupForContent.tsx

@@ -1,71 +0,0 @@
-import * as React from "react";
-import { View, StyleSheet } from "react-native";
-
-import { FocusableGroup } from "@applicaster/zapp-react-native-ui-components/Components/FocusableGroup";
-import { riverFocusManager } from "@applicaster/zapp-react-native-utils/appUtils/RiverFocusManager";
-
-import { topMenuLayoutChange$ } from "@applicaster/zapp-react-native-tvos-app/Layout/topMenu";
-
-const styles = StyleSheet.create({
-  flexOne: {
-    flex: 1,
-  },
-});
-
-export const withFocusableGroupForContent = (Component) => {
-  return function WithFocusableGroupForContent(props) {
-    const { screenId, isInsideContainer } = props;
-
-    const [topMenuHeight, setTopMenuHeight] = React.useState(0);
-
-    React.useEffect(() => {
-      const subscription = topMenuLayoutChange$.subscribe((layout) => {
-        setTopMenuHeight(layout.height);
-      });
-
-      return () => {
-        subscription.unsubscribe();
-      };
-    }, []);
-
-    const focusableId = React.useMemo(
-      () =>
-        riverFocusManager.screenFocusableGroupId({
-          screenId,
-          isInsideContainer,
-        }),
-      [screenId, isInsideContainer]
-    );
-
-    if (isInsideContainer) {
-      return <Component {...props} />;
-    }
-
-    return (
-      <FocusableGroup
-        key={focusableId}
-        id={focusableId}
-        // The top menu is rendered in its own FocusableGroup, anchored at the top of the screen.
-        // When the "content" FocusableGroup starts at y = 0 as well, the two groups visually overlap.
-        // On TvOS platform this overlap can confuse the focus engine, because the focusable bounds of
-        // the top-menu group and the content group intersect, leading to erratic navigation between
-        // the menu and the content (e.g. unexpected jumps or focus getting "stuck").
-        //
-        // To avoid this, we shift the entire content FocusableGroup down by the dynamic top menu
-        // height (marginTop: topMenuHeight). This separates the focus regions of the two groups in
-        // focus space, so they no longer intersect.
-        //
-        // The inner <View> below then applies the inverse margin (marginTop: -topMenuHeight) so that
-        // the actual visual position of the content on screen does not change; only the focusable
-        // bounds of the outer group are offset.
-        style={[styles.flexOne, { marginTop: topMenuHeight }]}
-        // this group does not have parent
-        groupId={undefined}
-      >
-        <View style={[styles.flexOne, { marginTop: -1 * topMenuHeight }]}>
-          <Component {...props} groupId={focusableId} />
-        </View>
-      </FocusableGroup>
-    );
-  };
-};

package/Helpers/DataSourceHelper/__tests__/itemLimitForData.test.ts

@@ -1,80 +0,0 @@
-import { itemLimitForData } from "..";
-
-describe("itemLimitForData (no mocks)", () => {
-  test("returns full array when item_limit is undefined (default Infinity)", () => {
-    // @ts-ignore
-    const result = itemLimitForData([1, 2, 3], {
-      rules: { item_limit: undefined },
-    });
-
-    expect(result).toEqual([1, 2, 3]);
-  });
-
-  test("enforces positive numeric item_limit", () => {
-    // @ts-ignore
-    const result = itemLimitForData([1, 2, 3, 4], {
-      rules: { item_limit: 2 },
-    });
-
-    expect(result).toEqual([1, 2]);
-  });
-
-  test("returns empty array when entry is empty", () => {
-    const result = itemLimitForData([], {
-      rules: { item_limit: 3 },
-    });
-
-    expect(result).toEqual([]);
-  });
-
-  test("defaults entry to empty array when it is undefined", () => {
-    const result = itemLimitForData(undefined, {
-      rules: { item_limit: 5 },
-    });
-
-    expect(result).toEqual([]);
-  });
-
-  test("handles missing component", () => {
-    // @ts-ignore
-    const result = itemLimitForData([10, 20, 30], undefined);
-    // missing component → item_limit = undefined → fallback to Infinity
-    expect(result).toEqual([10, 20, 30]);
-  });
-
-  test("handles missing rules object", () => {
-    // @ts-ignore
-    const result = itemLimitForData([10, 20, 30], {});
-
-    expect(result).toEqual([10, 20, 30]);
-  });
-
-  test("non-positive item_limit should fall back to Infinity", () => {
-    // @ts-ignore
-    const result = itemLimitForData([1, 2, 3], {
-      rules: { item_limit: -10 },
-    });
-
-    // -10 → invalid → fallback to Infinity → no limit
-    expect(result).toEqual([1, 2, 3]);
-  });
-
-  test("zero item_limit should fall back to Infinity", () => {
-    // @ts-ignore
-    const result = itemLimitForData([1, 2, 3], {
-      rules: { item_limit: 0 },
-    });
-
-    // 0 → invalid → fallback to Infinity
-    expect(result).toEqual([1, 2, 3]);
-  });
-
-  test("NaN item_limit should fall back to Infinity", () => {
-    // @ts-ignore
-    const result = itemLimitForData([1, 2, 3], {
-      rules: { item_limit: NaN },
-    });
-
-    expect(result).toEqual([1, 2, 3]);
-  });
-});

package/Helpers/DataSourceHelper/index.ts

@@ -1,19 +0,0 @@
-import { toPositiveNumberWithDefault } from "@applicaster/zapp-react-native-utils/numberUtils";
-
-export function itemLimitForData(
-  entry: ZappEntry[],
-  component: {
-    rules?: { item_limit?: number | string };
-  }
-) {
-  if (!component?.rules?.item_limit) {
-    return entry;
-  }
-
-  const itemLimit = toPositiveNumberWithDefault(
-    Infinity,
-    component?.rules?.item_limit
-  );
-
-  return (entry || []).slice(0, itemLimit);
-}