Is there any way to use the "disableDefinition" equivalent on the implementation side of the extension?

[yaegassy]

The LanguageClientOptions interface in coc.nvim allows for disableCompletion, disableSnippetCompletion, disableDiagnostics, and more.

For example, if you use two language servers (extension), you may want to disable the "definition" of only one of them. (Both provide a definition).

[fannheyward]

No disableDefinition API yet, you can use provideDefinition middleware to return null/undefined result if you want to disable it.

[fannheyward]

@yaegassy just return, no need to call next anymore because you didn't want it.

[fannheyward]

https://github.com/fannheyward/coc-deno/blob/master/client/src/extension.ts#L101

[yaegassy]

I am thinking of adding configuration to enable/disable it.

I'll refer to the coc-deno code! Thank you very much.

[fannheyward]

reruns null/undefined, not void, my mistake. https://github.com/neoclide/coc.nvim/blob/master/typings/index.d.ts#L2999-L3014

[yaegassy]

I was able to behave as I expected. Thanks @fannheyward.

(For future searchers)

  const clientOptions: LanguageClientOptions = {
    // ...snip
    middleware: {
      // ...snip
      provideDefinition: async (
        document: TextDocument,
        position: Position,
        token: CancellationToken,
        next: ProvideDefinitionSignature
      ) => {
        // ---- configuration ----
        if (disableDefinition) {
          return;
        }
        const def = await next(document, position, token);
        return def;
      },
    },
  };