{"version":"2.1.247","anchor":"plugins-loaded-from-a-directory-cannot-point-their-lsp-confi","canonical_anchor":"plugins-loaded-from-a-directory-cannot-point-their-lsp-confi","heading":"Plugins loaded from a directory cannot point their LSP config outside that directory","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/plugins-loaded-from-a-directory-cannot-point-their-lsp-confi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Plugins loaded from a directory cannot point their LSP config outside that directory\n\nA plugin's language-server config pointing outside its own folder is now skipped with a warning.\n\n**What**\n\nWhen a plugin loaded from a local directory supplies language-server configuration, both the top-level config file and each per-server config path are now resolved to their real location and skipped with a warning if they land outside the plugin's own directory.\n\n**Details**\n\n- The plugin directory, its parent chain and the target file are all resolved through symlinks before the comparison.\n- Applies to directory-loaded plugins only.\n\n**Evidence**\n\n`which a directory-loaded plugin may not reference here.`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}