@gjsify/react-native 0.53.0 → 0.54.0

package/lib/types/app-registry.d.ts

@@ -8,17 +8,15 @@ export type ComponentProvider = () => ComponentType<Record<string, unknown>>;
  * `runApplication`'s parameters: React Native's `initialProps` plus the window
  * shape, over the WHOLE option set of the application shell this layer runs on.
  *
- * `Omit<AdwaitaAppOptions, 'createWindow'>` rather than a hand-copied list of the
- * fields worth forwarding, and that is the load-bearing part. The shell owns
- * `devtools`, `about`, `onStartup`, `quitAction`, `flags` and `css`, each wired at
- * the lifecycle moment only the shell knows — `installDevtools` in particular MUST
- * run in `startup`, because the bus connection and object path exist only after the
- * application has registered, which is inside `runAdwaitaApp` and unreachable from
- * a consumer's entry file. A forwarding list would have to grow every time the shell
- * gains an option, and the field nobody remembered to add is exactly the one a
- * consumer needs: `devtools` was that field, and its absence is why an application
- * on this layer could not be driven from outside (#1455). `createWindow` is the one
- * option this layer answers itself — it renders the registered component.
+ * `Omit<AdwaitaAppOptions, 'createWindow'>` rather than a hand-copied list of the fields worth
+ * forwarding, and that is the load-bearing part. The shell owns `devtools`, `about`, `onStartup`,
+ * `quitAction`, `flags` and `css`, each wired at the lifecycle moment only the shell knows —
+ * `installDevtools` in particular MUST run in `startup`, because the bus connection and object path
+ * exist only after the application has registered, which is inside `runAdwaitaApp` and unreachable
+ * from a consumer's entry file. A forwarding list would have to grow every time the shell gains an
+ * option, and the field nobody remembered to add is exactly the one a consumer needs: `devtools`
+ * was that field, and its absence is why an application on this layer could not be driven from
+ * outside (#1455). `createWindow` is the one option this layer answers itself.
  */
 export interface RunApplicationOptions extends Omit<AdwaitaAppOptions, 'createWindow'> {
     /**
@@ -45,36 +43,29 @@ export declare const windowChromeChecks: () => number;
 /**
  * Everything `runApplication` hands the application shell, as a VALUE.
  *
- * A named function with a spec rather than an object literal inline, because the
- * defect it prevents is invisible at the call site: the previous shape listed
- * `applicationId` and `css` and dropped every other field, which reads as complete
- * and silently swallowed `devtools` — the option a consumer needs to be able to
- * drive their own application at all (#1455). `app-registry.spec.ts` asserts that
- * NOTHING is dropped, whatever it is, so re-introducing a field list fails for any
- * option rather than only for the ones a test happened to name.
+ * A named function with a spec rather than an object literal inline, because the defect it
+ * prevents is invisible at the call site: an inline shape that listed `applicationId` and `css` and
+ * dropped every other field reads as complete and silently swallowed `devtools` (#1455).
+ * `app-registry.spec.ts` asserts that NOTHING is dropped, whatever it is.
  *
- * `createWindow` last: it is the one option this layer answers itself, and a
- * consumer's `createWindow` must not be able to replace the React root.
+ * `createWindow` last: it is the one option this layer answers itself, and a consumer's
+ * `createWindow` must not be able to replace the React root.
  */
 export declare function toShellOptions(options: RunApplicationOptions, createWindow: (app: Adw.Application) => Gtk.Window): AdwaitaAppOptions;
 /**
  * Build the window, mount the registered component into it, publish the chrome.
  *
- * A NAMED FUNCTION AND NOT THE CLOSURE IT WAS, for the reason `window-chrome.ts` gives
- * one function earlier: the vectors have to measure THIS composition, and a spec that
- * rebuilt it by hand passes while the shipping shell drifts. That is #1549 as measured
- * — deleting `provideWindowChrome(chrome, …)` from the render call below left `oxfmt`
- * clean, `oxlint` at 0, `tsc` at 0 and the whole `@gjsify/react-native` suite green,
- * ten hand-written window-chrome vectors included, while the running application drew
- * two mapped `AdwHeaderBar`s: two sets of window controls, one dead close button
- * (#1460).
+ * A NAMED FUNCTION AND NOT THE CLOSURE IT WAS, for the reason `window-chrome.ts` gives one
+ * function earlier: the vectors have to measure THIS composition, and a spec that rebuilt it by hand
+ * passes while the shipping shell drifts. That is #1549 as measured — deleting
+ * `provideWindowChrome(chrome, …)` from the render call below left `oxfmt` clean, `oxlint` at 0,
+ * `tsc` at 0 and the whole `@gjsify/react-native` suite green, ten hand-written window-chrome
+ * vectors included, while the running application drew two mapped `AdwHeaderBar`s (#1460).
  *
- * The seam is HERE and not one call further out because `runApplication` cannot be
- * entered from a spec at all: it runs a `Gio.Application`, and a nested
- * `g_application_run` inside the test runner's own main loop never returns — measured,
- * `g_application_run: assertion '!application->priv->must_quit_now' failed` and a
- * timed-out case. Everything past this function is the shell's, and `toShellOptions`
- * already holds the hand-over to it.
+ * The seam is HERE and not one call further out because `runApplication` cannot be entered from a
+ * spec at all: it runs a `Gio.Application`, and a nested `g_application_run` inside the test
+ * runner's own main loop never returns — measured, `g_application_run: assertion
+ * '!application->priv->must_quit_now' failed` and a timed-out case.
  */
 export declare function mountApplicationRoot(app: Adw.Application, appKey: string, options: RunApplicationOptions, provider: ComponentProvider): Gtk.Window;
 /**

package/lib/types/primitives/table.d.ts

@@ -73,24 +73,21 @@ export interface RefusedRoute {
 /**
  * A prop the LAYER answers by calling a method when a signal fires.
  *
- * `accessibilityLiveRegion` is the whole of it, and the shape is forced by the
- * mismatch between the two platforms' models. React Native's prop is a DECLARATION
- * — "when this element's content changes, tell the user" — and the platform's
- * accessibility layer watches for the change. GTK has no such declaration: since
- * 4.14 it has `gtk_accessible_announce(self, message, priority)` (MEASURED on
- * gtk 4.22.4 — the method is on the `Gtk.Accessible` interface, so every widget has
- * it, and it takes a `GtkAccessibleAnnouncementPriority` of LOW/MEDIUM/HIGH), which
- * is an IMPERATIVE call: the caller supplies both the moment and the message.
+ * `accessibilityLiveRegion` is the whole of it, and the shape is forced by the mismatch between
+ * the two platforms' models. React Native's prop is a DECLARATION — "when this element's
+ * content changes, tell the user" — and the platform's accessibility layer watches for the
+ * change. GTK has no such declaration: since 4.14 it has `gtk_accessible_announce(self,
+ * message, priority)` (MEASURED on gtk 4.22.4 — on the `Gtk.Accessible` interface, so every
+ * widget has it), which is an IMPERATIVE call: the caller supplies both the moment and the
+ * message.
  *
- * So a live region can only be built where this layer knows both. It knows both on
- * exactly one primitive — `Text`, whose content IS one widget property, so
- * `notify::label` is the moment and `label` is the message. Everywhere else the
- * content is a SUBTREE and GTK emits nothing when one changes, which is why the
- * common route refuses the prop by name rather than this route answering it.
+ * So a live region can only be built where this layer knows both. It knows both on exactly one
+ * primitive — `Text`, whose content IS one widget property, so `notify::label` is the moment
+ * and `label` is the message. Everywhere else the content is a SUBTREE and GTK emits nothing
+ * when one changes, which is why the common route refuses the prop by name.
  *
- * Like {@link FileRoute} and {@link GestureRoute}, the table holds the whole of the
- * DECISION and none of the call: the priority is a `gi://Gtk` enum member and
- * nothing under `primitives/` imports `gi://`.
+ * Like {@link FileRoute} and {@link GestureRoute}, the table holds the whole of the DECISION
+ * and none of the call: nothing under `primitives/` imports `gi://`.
  */
 export interface AnnounceRoute {
     readonly to: 'announce';
@@ -124,14 +121,13 @@ export interface IgnoredRoute {
 /**
  * A prop whose value becomes a `Gio.File` — and the reason it is its own kind.
  *
- * `Gtk.Picture:file` takes a `Gio.File`, an OBJECT, and building one needs
- * `gi://Gio`. Nothing under `primitives/` imports `gi://` (that is what makes L2
- * testable without a display and reusable by a binding that never loads GTK), so the
- * table cannot produce the value — only the DECISION about it. So L2 does the whole
- * of the decision, which is where every refusal lives (`http:` has no synchronous
- * loader, a `require()` id has no asset registry, an array is a device-scale
- * picker), and hands the framework layer a `{ kind, value }` pair it turns into one
- * call: `Gio.File.new_for_path` or `Gio.File.new_for_uri`.
+ * `Gtk.Picture:file` takes a `Gio.File`, an OBJECT, and building one needs `gi://Gio`.
+ * Nothing under `primitives/` imports `gi://` (that is what makes L2 testable without a display
+ * and reusable by a binding that never loads GTK), so the table cannot produce the value —
+ * only the DECISION about it. So L2 does the whole of the decision, which is where every
+ * refusal lives (`http:` has no synchronous loader, a `require()` id has no asset registry, an
+ * array is a device-scale picker), and hands the framework layer a `{ kind, value }` pair it
+ * turns into one call.
  */
 export interface FileRoute {
     readonly to: 'file';
@@ -143,13 +139,12 @@ export interface FileRoute {
 /**
  * A prop bound through a gesture CONTROLLER rather than a signal on the widget.
  *
- * `TouchableWithoutFeedback` is the one primitive that needs it: it has no button
- * chrome, so its widget is a `Gtk.Box`, and a box emits no `clicked` (measured —
- * `Gtk.Button`'s two signals are `activate` and `clicked`, and a box has neither).
- * The desktop answer is a `Gtk.GestureClick` added to the widget, whose `released`
- * signal is the press completing. A controller is `add_controller(new
- * Gtk.GestureClick())` — a constructed OBJECT, so the same rule as {@link FileRoute}
- * applies: the table names the signal, the framework layer builds the controller.
+ * `TouchableWithoutFeedback` is the one primitive that needs it: it has no button chrome, so
+ * its widget is a `Gtk.Box`, and a box emits no `clicked` (measured — `Gtk.Button`'s two
+ * signals are `activate` and `clicked`, and a box has neither). The desktop answer is a
+ * `Gtk.GestureClick` added to the widget, whose `released` signal is the press completing. A
+ * controller is a constructed OBJECT, so the same rule as {@link FileRoute} applies: the table
+ * names the signal, the framework layer builds the controller.
  */
 export interface GestureRoute {
     readonly to: 'gesture';

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

@@ -8,12 +8,11 @@ export interface TabScreenOptions {
     /**
      * 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".
+     * 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.
@@ -23,33 +22,25 @@ export interface TabScreenOptions {
 /**
  * Put the stack on the focused page, or leave it alone because that page is not there yet.
  *
- * THE PRESENCE CHECK IS THE TERMINATING CONDITION, and the reason it has to be explicit is
- * that the obvious guard is a bet rather than a test. Writing
- *
- *     if (stack.get_visible_child_name() !== focused) stack.set_visible_child_name(focused);
- *
- * reads as "set it unless it is already set", and it terminates only when the set TAKES.
+ * THE PRESENCE CHECK IS THE TERMINATING CONDITION, and the obvious guard is a bet rather than a
+ * test. Writing `if (stack.get_visible_child_name() !== focused) stack.set_visible_child_name(
+ * focused)` reads as "set it unless it is already set", and it terminates only when the set TAKES.
  * MEASURED on libadwaita 1.9.3: `set_visible_child_name` with a name the stack does not hold
- * changes nothing, emits NO `notify::visible-child-name`, and prints
- * `Adwaita-WARNING: Child name '…' not found in AdwViewStack`. So `get_visible_child_name()`
- * still answers the old page, the comparison is still unequal, and the effect — which has no
- * dependency array on purpose, because a page can materialise on a render where `focused` did
- * not change — repeats the failing call on every render for as long as the mismatch lasts.
+ * changes nothing, emits NO `notify::visible-child-name`, and prints `Adwaita-WARNING: Child name
+ * '…' not found in AdwViewStack`. So the getter still answers the old page, the comparison is
+ * still unequal, and the effect — which has no dependency array on purpose, because a page can
+ * materialise on a render where `focused` did not change — repeats the failing call on every
+ * render for as long as the mismatch lasts.
  *
- * A focused route whose page React has not committed yet is an ORDINARY intermediate state,
- * not a fault: the effect runs after the commit that added the OTHER pages, and the missing
- * one arrives on a later commit. So the answer is to do nothing and let the next render try,
- * which is what "not there yet" deserves — and one warning per render for a normal state is
- * how a log stops being read.
+ * A focused route whose page React has not committed yet is an ORDINARY intermediate state, not a
+ * fault, so the answer is to do nothing and let the next render try — one warning per render for a
+ * normal state is how a log stops being read.
  *
- * AND THE SET HAS A SECOND WAY TO DO NOTHING, which is why presence alone is not the whole
- * gate. `adw_view_stack_set_visible_child_name` ends on
- * `if (gtk_widget_get_visible (page->widget)) set_visible_child (...)`, so a page that is
- * there but HIDDEN changes nothing, emits no notify and — unlike the missing name — prints
- * NOTHING AT ALL (measured). That is the same non-terminating state by the quieter road: the
- * caller would be told the stack shows `focused` while it shows the other page, and no log
- * anywhere would disagree. Both no-op paths are therefore asked about BEFORE the write, which
- * is also what keeps each one attributable to its own failing assertion.
+ * AND THE SET HAS A SECOND WAY TO DO NOTHING, which is why presence alone is not the whole gate.
+ * `adw_view_stack_set_visible_child_name` ends on `if (gtk_widget_get_visible (page->widget))
+ * set_visible_child (...)`, so a page that is there but HIDDEN changes nothing, emits no notify and
+ * — unlike the missing name — prints NOTHING AT ALL (measured). That is the same non-terminating
+ * state by the quieter road. Both no-op paths are therefore asked about BEFORE the write.
  *
  * @returns whether the stack now shows `focused`.
  */

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gjsify/react-native",
-    "version": "0.53.0",
+    "version": "0.54.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.53.0",
-        "@gjsify/gtk-host": "^0.53.0"
+        "@gjsify/adwaita-app": "^0.54.0",
+        "@gjsify/gtk-host": "^0.54.0"
     },
     "peerDependencies": {
         "@react-navigation/core": "^7.21.13",
@@ -152,9 +152,9 @@
         "@girs/gdk-4.0": "5.4.0",
         "@girs/gjs": "5.4.0",
         "@girs/gtk-4.0": "5.4.0",
-        "@gjsify/cli": "^0.53.0",
-        "@gjsify/rolldown-plugin-gjsify": "^0.53.0",
-        "@gjsify/unit": "^0.53.0",
+        "@gjsify/cli": "^0.54.0",
+        "@gjsify/rolldown-plugin-gjsify": "^0.54.0",
+        "@gjsify/unit": "^0.54.0",
         "@react-navigation/core": "^7.21.13",
         "@react-navigation/routers": "^7.6.4",
         "@types/node": "^25.9.2",