convex-feedback-ui 0.2.0-beta.4 → 0.2.0-beta.6

package/README.md

@@ -1,4 +1,4 @@
-[![npm version](https://badge.fury.io/js/convex-feedback-ui.svg)](https://badge.fury.io/js/convex-feedback-ui) [![Convex Component](https://www.convex.dev/components/badge/convex-feedback)](https://www.convex.dev/components/convex-feedback) ![NPM License](https://img.shields.io/npm/l/convex-feedback-ui) ![NPM Downloads](https://img.shields.io/npm/dw/convex-feedback-ui) ![GitHub forks](https://img.shields.io/github/forks/moumen-io/convex-feedback) ![GitHub Repo stars](https://img.shields.io/github/stars/moumen-io/convex-feedback)
+![npm version](https://badge.fury.io/js/convex-feedback-ui.svg) ![Convex Component](https://www.convex.dev/components/badge/convex-feedback) ![NPM License](https://img.shields.io/npm/l/convex-feedback-ui) ![NPM Downloads](https://img.shields.io/npm/dw/convex-feedback-ui) ![GitHub forks](https://img.shields.io/github/forks/moumen-io/convex-feedback) ![GitHub Repo stars](https://img.shields.io/github/stars/moumen-io/convex-feedback)
 
 [Vite demo](https://convex-feedback-vite.vercel.app/) • [Expo demo](https://convex-feedback-expo.vercel.app/) • [React Native demo](https://convex-feedback-native.vercel.app/)
 
@@ -98,6 +98,8 @@ import { FeedbackScreen } from "convex-feedback-ui/native";
 
 The native `FeedbackScreen` includes the feedback UI using React Native components.
 
+The native roadmap exports also include the reusable `RoadmapBoard` and `RoadmapScreenContent`. Their `topInset` defaults to `0`, while `bottomInset` defaults to the bottom safe-area inset. These props describe space occupied by host navigation chrome: an explicit `bottomInset` is the total space, including the safe area, and replaces the default even when set to `0`. NativeTabs normally bounds content above its tab bar, so it should be left unset there.
+
 ## Expo Router
 
 Expo Router projects can use the `/expo` entry point:
@@ -164,6 +166,12 @@ its text label:
 />
 ```
 
+### Roadmap stack insets
+
+The stack-enabled Expo `RoadmapScreen` and routed `RoadmapStackLayout` use a transparent native header by default. The board automatically reserves the measured native-stack header height; if that context is unavailable, the fallback is 44 points on iOS or 56 points on Android, plus the top safe-area inset. If `headerTransparent` is `false`, the native stack already places the board below the header and the automatic top inset is `0`. Set `topInset` to override that space, including with `0`.
+
+The routed and stack-enabled roadmap also renders its native bottom search toolbar on iOS 26 and newer and includes its standard 44-point height in the default `bottomInset`. Android and older iOS versions do not receive an empty toolbar. If your host draws a toolbar or tab bar over the screen, pass `bottomInset` as the total occupied height, including the safe area; an explicit value replaces the automatic default, including `0`. NativeTabs content is already bounded above the tab bar, so omit `bottomInset` there.
+
 ### Using the Expo screen without stack integration
 
 Expo projects do not have to use the native stack integration.
@@ -279,12 +287,7 @@ export default function Layout() {
 }
 ```
 
-The board's search and loaded list remain mounted when another screen is
-pushed, so returning restores the prior query and scroll position. The create
-route is a modal navigator by default. Duplicate suggestions push the normal
-detail screen inside that modal's stack, with back and close controls. After
-creation, the complete modal is dismissed and the created entry replaces it on
-the board stack.
+The board's search and loaded list remain mounted when another screen is pushed, so returning restores the prior query and scroll position. The create route is a modal navigator by default. Duplicate suggestions push the normal detail screen inside that modal's stack, with back and close controls. After creation, the complete modal is dismissed and the created entry replaces it on the board stack.
 
 See `packages/example-expo-routed` for a complete application.
 
@@ -328,6 +331,10 @@ entry route is supplied. The board title and search field are rendered by the
 Expo Router Stack, and `RoadmapBoard` is exported from the native entry points
 for sharing the admin-style stage layout with custom cards.
 
+On this routed stack, `topInset` and `bottomInset` can be supplied on
+`RoadmapStackLayout` to replace the automatic header and bottom-toolbar
+spacing.
+
 ## Diagnostic metadata
 
 Prebuilt screens can collect creation-time diagnostic metadata for feedback entries. Collection is disabled by default and never applies to comments.
@@ -367,7 +374,6 @@ Or combine global defaults with per-kind behavior:
 - A kind set to `false` disables all metadata collection for that kind.
 - Collection happens only when the user finally submits.
 - Unavailable or failed collection sources are omitted without blocking feedback submission.
-
 - Web defaults include `platform`, `user agent`, `language`, `timezone`, `screen` and `viewport` dimensions, and `device pixel ratio`.
 - React Native defaults include `platform`, `OS` version, available device model, screen `dimensions`, `pixel ratio`, and `font scale`.
 - The Expo entry point additionally uses `expo-constants` for app `version`, `build` number, `application ID`, `Expo runtime version`, and execution `environment` when available.