{"version":"2.1.248","anchor":"language-server-tool-takes-one-operation-field-instead-of-ni","canonical_anchor":"language-server-tool-takes-one-operation-field-instead-of-ni","heading":"Language-server tool takes one operation field instead of nine shapes","tier":"internal","area":"IDE Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/language-server-tool-takes-one-operation-field-instead-of-ni","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Language-server tool takes one operation field instead of nine shapes\n\nThe IDE language-server tool now takes a single operation field instead of nine input shapes.\n\n**What**\n\nThe IDE language-server tool's input is now a single object with an `operation` enum rather than nine near-identical alternatives, and it declares an output shape of result and filePath plus optional resultCount and fileCount.\n\n**Details**\n\n- Query guidance moved to the shared field: \"The symbol name or partial name to search for (workspaceSymbol only). Most language servers return no results for an empty query, so always provide it when using workspaceSymbol.\"\n\n**Evidence**\n\n`The symbol name or partial name to search for (workspaceSymbol only). Most language servers return no results for an empty query, so always provide it when using workspaceSymbol.`\n\n- Area: IDE Integration\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}