From 26ce16584ecd5fa7d586e9e0ef0d5313c75659cb Mon Sep 17 00:00:00 2001
From: GRAVATAR-HOVERCARDS <254200944+gitme1-ym@users.noreply.github.com>
Date: Tue, 20 Jan 2026 17:27:58 -0500
Subject: [PATCH] Update composition-api-faq.md

---
 src/guide/extras/composition-api-faq.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/guide/extras/composition-api-faq.md b/src/guide/extras/composition-api-faq.md
index e715cefc2c..681e8850fa 100644
--- a/src/guide/extras/composition-api-faq.md
+++ b/src/guide/extras/composition-api-faq.md
@@ -157,3 +157,4 @@ In comparison, Vue Composition API:
 - No need to manually cache callback functions to avoid unnecessary child updates. In general, Vue's fine-grained reactivity system ensures child components only update when they need to. Manual child-update optimizations are rarely a concern for Vue developers.
 
 We acknowledge the creativity of React Hooks, and it is a major source of inspiration for Composition API. However, the issues mentioned above do exist in its design and we noticed Vue's reactivity model happens to provide a way around them.
+https://github.com/microsoft/vscode-wiki.git