fix(mongodb): skip SQL semantic diagnostics for MongoDB connections

MongoDB shell syntax like db.collection.find({}) was incorrectly
parsed as SQL, causing a "sql parser error" diagnostic in the editor.
Added MongoDB guards in shouldRunSqlSemanticDiagnostics and
refreshSemanticDiagnostics, matching existing Elasticsearch logic.

Also fix a pre-existing TiDB cloud URL param ordering test failure.
This commit is contained in:
t8y2 committed 2026-06-09 16:20:50 +08:00
1 parent 7798f2231e
commit 6a14b11efc
4 files changed
+24 -3

No files matched your search

@@ -741,7 +741,7 @@ async function refreshSemanticDiagnostics() {
setSemanticDiagnostics([]);
return;
}
if (props.databaseType === "elasticsearch") {
if (props.databaseType === "mongodb" || props.databaseType === "elasticsearch") {
setSemanticDiagnostics([]);
return;
}