@gjsify/react-native 0.48.0 → 0.50.0

package/lib/types/prop-table.d.ts

@@ -1,6 +1,6 @@
-import { type PropAnswer, type PropStatus } from './primitives/answers.js';
+import { type PropAnswer, type PropStatus, type ValueVocabulary } from './primitives/answers.js';
 import { PRIMITIVE_NAMES } from './primitives/table.js';
-export type { PropAnswer, PropStatus };
+export type { PropAnswer, PropStatus, ValueVocabulary };
 /**
  * Every primitive this layer answers for.
  *
@@ -68,11 +68,29 @@ export declare function acceptsPropValue(primitive: string, prop: string, value:
  * under Node type stripping is why) — so the formatter the throw uses lives in
  * `errors.ts` and both call it.
  *
- * A value merely ABSENT from a mapped prop's table is NOT answered here: that is the
- * "Known: …" a typo gets, it is built from the map at the moment of the throw, and this
- * surface is about the values the table refuses ON PURPOSE.
+ * TWO GRAINS OF REFUSAL, AND THE SECOND ONE WAS MISSING (#1648). A prop can refuse a
+ * value by NAME — `answer.refuses`, a deny-list with a reason per entry — and it can
+ * refuse one by OMISSION from the list its route maps: `pointerEvents` is
+ * `{ auto, none }`, `box-none` is a real React Native spelling with no GTK
+ * expression, and a render throws on it. Reading only the deny-list answered ACCEPTED
+ * for the second kind on every mapped property, every `announce` route and every
+ * accessible record — and a consumer deleted a working `box-none` mapping of their
+ * own because a green test said the layer had caught up.
+ *
+ * What is still NOT answered here is the TYPE grain: `coerce` refuses a non-boolean
+ * for `editable` and a non-function for `onPress`, and neither is a list this table
+ * can publish. `acceptsPropValue` is an oracle for the vocabulary, not for the type.
  */
 export declare function explainPropValue(primitive: string, prop: string, value: unknown, variant?: PropVariant): string | null;
+/**
+ * The values this prop accepts by name, or `null` when the table enumerates none.
+ *
+ * The reader for {@link PropAnswer.allows}, beside `propRefusedValues` because they
+ * are the two halves of one question and a consumer holding a ledger of "which props
+ * has the layer caught up on" needs both: a deny-list says which spellings have a
+ * reason, an allow-list says which ones exist at all.
+ */
+export declare function propAllowedValues(primitive: string, prop: string, variant?: PropVariant): readonly string[] | null;
 /** Every prop name this primitive's table row carries, sorted. Framework props are not among them. */
 export declare function propNames(primitive: string, variant?: PropVariant): readonly string[];
 /**

package/lib/types/router/tabs.d.ts

@@ -1,10 +1,24 @@
 import { type ReactElement, type ReactNode } from 'react';
-import type Adw from '@girs/adw-1';
+import Adw from 'gi://Adw?version=1';
 import { type ScreenDeclaration } from './screens.js';
 /** What one tab can be told. */
 export interface TabScreenOptions {
     /** The switcher button's label. Defaults to the route name. */
     title?: string;
+    /**
+     * The switcher button's icon, as an icon-theme name (`go-home-symbolic`).
+     *
+     * NOT OPTIONAL DECORATION, which is why it is here rather than left to the
+     * application. `Adw.ViewSwitcher` reserves the icon whether or not one is set —
+     * MEASURED, the same five tabs measure 317/647 px with icons and without — and a
+     * page with no `icon-name` draws the icon theme's missing-image glyph in the space
+     * it reserved. So the choice was never "icons or no icons"; it was "your icon or a
+     * broken one".
+     *
+     * A name the theme does not carry draws that same glyph, and nothing says so.
+     * `Gtk.IconTheme.has_icon()` is the check worth running when picking one.
+     */
+    iconName?: string;
 }
 /**
  * Put the stack on the focused page, or leave it alone because that page is not there yet.
@@ -53,8 +67,39 @@ export interface TabsProps {
     children?: ReactNode;
     /** Options for every tab, before its own. */
     screenOptions?: TabScreenOptions;
-    /** `false` drops the header bar, and with it the switcher. */
+    /** `false` drops the header bar, and with it the switcher and the bottom bar. */
     headerShown?: boolean;
+    /**
+     * A persistent bar between the content and the switcher bar — a now-playing strip,
+     * a selection toolbar, an offline notice.
+     *
+     * ## Why a prop rather than a child
+     *
+     * `<Tabs>` reads its children as `<Tabs.Screen>` DECLARATIONS and refuses anything
+     * else by name, so there is no child position to put this in. And an app cannot
+     * wrap `<Tabs>` from outside either: the switcher is created with `slot: 'title'`,
+     * which resolves against the PARENT, so a box placed between a tab layout and the
+     * header bar takes the switcher's slot away and the router refuses it. A consumer
+     * hit exactly that and recorded "no mini player" as a limitation for weeks.
+     *
+     * ## Where it lands, measured
+     *
+     * `Adw.ToolbarView`'s `bottom` slot is an ADDER, so it takes this and the switcher
+     * bar together, and the order decides the stacking. MEASURED on libadwaita 1.9.3 in a
+     * 480x320 window: with two bottom bars added in sequence, the FIRST sits closer to
+     * the content — content at y=0 h=214, first-added at y=217, second-added at y=257.
+     * So this is rendered BEFORE the switcher bar, which puts it above it, which is
+     * where a phone puts a now-playing strip relative to its tab bar.
+     *
+     * Wrapped in a `Gtk.Box` rather than slotted directly, so that a caller can hand
+     * over any node — including a fragment or a component whose root element it does
+     * not control — without having to know that a slot name is involved.
+     *
+     * NOT RENDERED under `headerShown: false`, which drops the whole toolbar view and
+     * has nowhere to put it. Named here rather than worked around, because a navigator
+     * that asked for no chrome getting a bar anyway would be the greater surprise.
+     */
+    bottomBar?: ReactNode;
 }
 /**
  * `expo-router`'s `<Tabs>`: its tabs are the FILES this `_layout` owns.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gjsify/react-native",
-    "version": "0.48.0",
+    "version": "0.50.0",
     "description": "The React Native view vocabulary rendered onto GTK4/Adwaita, over @gjsify/gtk-host",
     "type": "module",
     "module": "lib/esm/index.js",
@@ -120,8 +120,8 @@
         "react-native"
     ],
     "dependencies": {
-        "@gjsify/adwaita-app": "^0.48.0",
-        "@gjsify/gtk-host": "^0.48.0"
+        "@gjsify/adwaita-app": "^0.50.0",
+        "@gjsify/gtk-host": "^0.50.0"
     },
     "peerDependencies": {
         "@react-navigation/core": "^7.21.13",
@@ -148,13 +148,13 @@
         }
     },
     "devDependencies": {
-        "@girs/adw-1": "4.6.0",
-        "@girs/gdk-4.0": "4.6.0",
-        "@girs/gjs": "4.6.0",
-        "@girs/gtk-4.0": "4.6.0",
-        "@gjsify/cli": "^0.48.0",
-        "@gjsify/rolldown-plugin-gjsify": "^0.48.0",
-        "@gjsify/unit": "^0.48.0",
+        "@girs/adw-1": "5.0.0",
+        "@girs/gdk-4.0": "5.0.0",
+        "@girs/gjs": "5.0.0",
+        "@girs/gtk-4.0": "5.0.0",
+        "@gjsify/cli": "^0.50.0",
+        "@gjsify/rolldown-plugin-gjsify": "^0.50.0",
+        "@gjsify/unit": "^0.50.0",
         "@react-navigation/core": "^7.21.13",
         "@react-navigation/routers": "^7.6.4",
         "@types/node": "^25.9.2",