Skip to content

Commit a9781ba

Browse files
committed
test(e2e): 52 asserts xim is NOT injected into project .xlings.json (matches fix)
The fake-xlings in 52_local_path_namespaced_index.sh asserted the OLD behavior (project .xlings.json must contain the official xim index). Flip it: xim is a global-default index and must NOT be injected project-scoped. Verified: e2e 52 OK. Claude-Session: https://claude.ai/code/session_01Y3KE7MAE8yV7BG35eXy7FV
1 parent 78e785d commit a9781ba

1 file changed

Lines changed: 6 additions & 2 deletions

File tree

tests/e2e/52_local_path_namespaced_index.sh

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -134,8 +134,12 @@ if [[ "${1:-}" == "interface" && "${2:-}" == "install_packages" ]]; then
134134
fi
135135
shift
136136
done
137-
if ! grep -q '"name": "xim"' "${XLINGS_PROJECT_DIR:?}/.xlings.json"; then
138-
echo "missing official xim index in project .xlings.json" >&2
137+
# The official global `xim` index must NOT be injected into the project's
138+
# .xlings.json — it's a global-default index (global IS the default scope);
139+
# injecting it project-scoped mis-scopes every xim:* tool into the project
140+
# store. Only user-declared local custom indices belong here.
141+
if grep -q '"name": "xim"' "${XLINGS_PROJECT_DIR:?}/.xlings.json"; then
142+
echo "official xim index must NOT be injected into project .xlings.json" >&2
139143
cat "${XLINGS_PROJECT_DIR:?}/.xlings.json" >&2 2>/dev/null || true
140144
exit 24
141145
fi

0 commit comments

Comments
 (0)