@idealyst/mcp-server 1.2.119 → 11.2.120

package/dist/index.cjs

@@ -3141,17 +3141,23 @@ navigator.navigate({ path: '/new-location', replace: true });
 
 ## useParams Hook
 
-Access current route path parameters. Returns \`Record<string, string>\`.
+Access current route path parameters. Returns \`Record<string, string | undefined>\`.
 
 > **WARNING:** \`useParams()\` does NOT accept generic type arguments. Do NOT write \`useParams<{ id: string }>()\` \u2014 this causes TS2558. Access params by key from the returned record instead.
 
+> **IMPORTANT:** Param values are \`string | undefined\`, NOT \`string\`. When passing a param to a function that expects \`string\`, you MUST handle the undefined case \u2014 either with a fallback (\`params.id ?? ''\`), a guard (\`if (!params.id) return null\`), or a non-null assertion (\`params.id!\`) if you are certain it exists. Without this, TypeScript will report TS2345.
+
 \`\`\`tsx
 import { useParams } from '@idealyst/navigation';
 
 function UserScreen() {
   // CORRECT \u2014 no type argument
   const params = useParams();
-  const userId = params.id;        // Path param from /user/:id
+  const userId = params.id;        // string | undefined from /user/:id
+
+  // Handle undefined before using in typed contexts:
+  if (!userId) return <Text>User not found</Text>;
+  // Now userId is narrowed to string
 
   // WRONG \u2014 useParams does NOT accept generics
   // const params = useParams<{ id: string }>();  // TS2558 error!
@@ -3162,26 +3168,37 @@ function UserScreen() {
 
 ## useNavigationState Hook
 
-Access navigation state passed via the \`state\` property:
+Access navigation state passed via the \`state\` property.
+
+> **IMPORTANT \u2014 Type constraints:**
+> - \`navigate({ state: {...} })\` requires all values to be \`string | number | boolean\` \u2014 NO \`undefined\` or \`null\`. Do NOT spread objects that may contain undefined values.
+> - \`useNavigationState<T>()\` requires \`T extends Record<string, unknown>\`. Use \`Record<string, string | number | boolean>\` for the type parameter, or a specific interface with NON-optional fields.
+> - **Do NOT use optional fields (\`?\`) in the type parameter** \u2014 values passed via state are always present (they were explicitly set by navigate()). Use required fields instead.
 
 \`\`\`tsx
 import { useNavigationState } from '@idealyst/navigation';
 
-// When navigating:
+// When navigating \u2014 all values must be string | number | boolean:
 navigator.navigate({
   path: '/recording',
   state: { autostart: true, source: 'home' }
 });
 
-// In destination screen:
+// In destination screen \u2014 use REQUIRED fields (not optional):
 function RecordingScreen() {
-  const { autostart, source } = useNavigationState<{
-    autostart?: boolean;
-    source?: string;
+  const state = useNavigationState<{
+    autostart: boolean;
+    source: string;
   }>();
 
-  // autostart = true, source = 'home'
+  // state.autostart = true, state.source = 'home'
 }
+
+// For multi-step wizards, pass ALL accumulated data as required fields:
+navigator.navigate({
+  path: '/step3',
+  state: { firstName: name, lastName: last, theme: selectedTheme }
+});
 \`\`\`
 
 ### Consuming State (Web)
@@ -11239,13 +11256,17 @@ var componentMetadata = {
       "Standard, alert, and confirmation types",
       "Title and close button",
       "Backdrop click to close",
-      "Animation types (slide, fade)"
+      "Animation types (slide, fade)",
+      "avoidKeyboard prop shifts dialog when keyboard opens (native)",
+      "height prop gives dialog a definite height so children can use flex: 1",
+      "Content area has flex: 1 \u2014 children can flex into available space"
     ],
     bestPractices: [
       "Use sparingly for important interactions",
       "Provide clear actions for dismissal",
       "Keep dialog content focused",
-      "Use confirmation dialogs for destructive actions"
+      "Use confirmation dialogs for destructive actions",
+      "Use height or maxContentHeight when children need flex-based sizing"
     ]
   },
   Divider: {
@@ -11590,12 +11611,14 @@ var componentMetadata = {
       "Multiple sizes",
       "Character count",
       "Auto-resize",
-      "Error state"
+      "Error state",
+      "fill prop for flex-based sizing (fills available space)"
     ],
     bestPractices: [
       "Use for multi-line input",
       "Show character limits when applicable",
-      "Provide appropriate placeholder text"
+      "Provide appropriate placeholder text",
+      "Use fill prop inside Dialog with avoidKeyboard to shrink with keyboard"
     ]
   },
   TextInput: {
@@ -20879,8 +20902,8 @@ These are mistakes agents make repeatedly. Each one causes TypeScript compilatio
 11. **NavigatorProvider** takes a \`route\` prop (SINGULAR) \u2014 NOT \`routes\`: \`<NavigatorProvider route={routeConfig} />\`. There is NO \`Router\` export.
 12. Use \`useNavigator()\` \u2014 NOT \`useNavigate()\`.
 13. \`navigate()\` takes an **object**: \`navigate({ path: '/settings' })\` \u2014 NOT \`navigate('/settings')\` or \`navigate('routeName', params)\`. To pass data use \`vars\`: \`navigate({ path: '/detail/:id', vars: { id: '123' } })\` \u2014 NOT \`params\`: \`navigate({ path: '/detail', params: { id: '123' } })\` (no \`params\` property exists).
-14. \`useNavigationState\` returns \`Record<string, unknown>\` by default. Always provide a type parameter: \`useNavigationState<{ title?: string }>()\`.
-15. \`useParams()\` does NOT accept generic type arguments. It returns \`Record<string, string>\`. Do NOT write \`useParams<{ id: string }>()\` \u2014 that causes TS2558.
+14. \`navigate({ state: {...} })\` values must be \`string | number | boolean\` \u2014 NO \`undefined\`, \`null\`, or objects. When forwarding state across wizard steps, ensure all values are defined before passing: \`navigate({ path: '/step2', state: { firstName: name, age: 25 } })\`. Do NOT use optional fields in state types.
+15. \`useParams()\` does NOT accept generic type arguments. It returns \`Record<string, string | undefined>\`. Do NOT write \`useParams<{ id: string }>()\` \u2014 that causes TS2558. Always guard for undefined: \`const id = params.id; if (!id) return null;\`.
 
 ### Imports & Styling
 16. **Never** import from \`react-native\` \u2014 no \`TouchableOpacity\`, \`FlatList\`, \`ScrollView\`, \`Animated\`, \`Dimensions\`, \`Linking\`, \`Platform\`. Idealyst provides cross-platform alternatives for all of these (e.g., \`openExternalLinks\` on Markdown, \`Pressable\` from \`@idealyst/components\`). **\`ScrollView\` is NOT exported from \`@idealyst/components\`** \u2014 use \`<View scrollable>\` instead. Do NOT \`import { ScrollView } from '@idealyst/components'\` \u2014 it will cause a TS import error.
@@ -70352,7 +70375,7 @@ function postProcessComponentTypes(componentName, result) {
   }
   if (componentName.toLowerCase() === "textarea") {
     if (typeof result === "object" && result !== null) {
-      result.usageNote = "TextArea has a DIFFERENT API from TextInput. TextArea uses onChange (not onChangeText) and does NOT have onBlur. TextArea DOES support label, error, and rows props (TextInput does NOT support label/error). Always call get_component_types('TextArea') separately \u2014 do NOT assume it shares TextInput's props.";
+      result.usageNote = "TextArea has a DIFFERENT API from TextInput. TextArea uses onChange (not onChangeText) and does NOT have onBlur. TextArea DOES support label, error, and rows props (TextInput does NOT support label/error). TextArea supports `fill` prop: when true, all container layers get flex: 1 so the textarea expands to fill available vertical space (useful inside Dialog with avoidKeyboard). Always call get_component_types('TextArea') separately \u2014 do NOT assume it shares TextInput's props.";
     }
   }
   if (componentName.toLowerCase() === "image") {