docs: add addendum on useId usage with computed

bencodezen · bencodezen · commit 1cc7db4f1b9a · 2025-07-08T09:19:37.000-04:00
diff --git a/src/api/composition-api-helpers.md b/src/api/composition-api-helpers.md
@@ -42,10 +42,11 @@ This is the underlying helper that powers [`defineModel()`](/api/sfc-script-setu
     set?: (v: T) => any
   }
 
-  type ModelRef<T, M extends PropertyKey = string, G = T, S = T> = Ref<G, S> & [
-    ModelRef<T, M, G, S>,
-    Record<M, true | undefined>
-  ]
+  type ModelRef<T, M extends PropertyKey = string, G = T, S = T> = Ref<
+    G,
+    S
+  > &
+    [ModelRef<T, M, G, S>, Record<M, true | undefined>]
   ```
 
 - **Example**
@@ -132,3 +133,20 @@ Used to generate unique-per-application IDs for accessibility attributes or form
   IDs generated by `useId()` are also guaranteed to be stable across the server and client renders, so they can be used in SSR applications without leading to hydration mismatches.
 
   If you have more than one Vue application instance of the same page, you can avoid ID conflicts by giving each app an ID prefix via [`app.config.idPrefix`](/api/application#app-config-idprefix).
+
+  :::warning Caution
+  `useId()` should be not be called inside a `computed()` property due to potential instance conflicts. Instead, it should be declared outside of `computed()` before the value is called inside of the computed function.
+
+  ```vue
+  <script setup>
+  import { computed, useId } from 'vue'
+
+  const id = useId()
+
+  const modifiedId = computed(
+    () => `${id}-${Math.floor(Math.random() * 10)}`
+  )
+  </script>
+  ```
+
+  :::
