Skip to content

docs: fix misleading getMongoClient() JSDoc#696

Open
hanhan761 wants to merge 1 commit into
microsoft:mainfrom
hanhan761:docs-643-fix-getmongo-jsdoc
Open

docs: fix misleading getMongoClient() JSDoc#696
hanhan761 wants to merge 1 commit into
microsoft:mainfrom
hanhan761:docs-643-fix-getmongo-jsdoc

Conversation

@hanhan761

Copy link
Copy Markdown

@

Summary

Fix the getMongoClient() JSDoc which incorrectly stated the method is used by the query playground evaluator. The playground worker runs in its own worker_thread with a separate MongoClient instance. The sole caller is actually scanCollectionSchema on the extension host main thread.

Issue

Fixes #643
@

@
docs: fix misleading getMongoClient() JSDoc

The JSDoc claimed getMongoClient() is used by the query playground
evaluator, but the playground worker has its own MongoClient in a
separate worker_thread/V8 isolate. The sole caller is actually
scanCollectionSchema which runs on the extension host main thread.

Closes microsoft#643
@
Copilot AI review requested due to automatic review settings May 29, 2026 13:27
@hanhan761 hanhan761 requested a review from a team as a code owner May 29, 2026 13:27
@tnaum-ms tnaum-ms added the in-triage-queue We've seen your input and will triage it label Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

in-triage-queue We've seen your input and will triage it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Revisit: getMongoClient() JSDoc is misleading; only used by main thread scanCollectionSchema

2 participants