dls ~dls-format

D Language Server

DUB	Travis	AppVeyor

LSP compliance: `3.13`

This is still a work in progress; there might still be bugs and crashes

DLS implements the server side of the Language Server Protocol (LSP) for the D programming language. It doesn't do much itself (yet), and rather uses already available components, and provides an interface to work with the LSP. Current features include:

• Code completion
• Going to symbol definition
• Finding references
• Symbol renaming
• Error checking
• Code formatting (document, range and on-type)
• Symbol listing (current document and workspace-wide)
• Symbol highlighting
• Documentation on hover
• Random, frustrating crashes

Packages used (the stuff doing the actual hard work):

• dcd
• dfmt
• dscanner
• dsymbol
• dub
• emsi_containers
• inifiled
• libddoc
• libdparse
• msgpack-d
• stdx-allocator

Usage

Some editors may need DLS to be installed manually (don't worry, it's easy).

Some common editors

• Visual Studio Code: install the extension
• Atom: install the package
• Sublime Text (using tomv654's LSP client):

  "clients":
  {
      "dls":
      {
          "command":
          [
              "[path to dls executable]"
          ],
          "enabled": true,
          "languageId": "d",
          "scopes":
          [
              "source.d"
          ],
          "syntaxes":
          [
              "Packages/D/D.sublime-syntax"
          ]
      }
  }
  

DLS should work with other editors, although your mileage may vary since it's moslty tested on the ones above. If it's not working with your editor of choice, submit an issue!

Command line options

Some command line options exist to control the behavior of DLS:

• --stdio: use standard input and output streams for communication
• --socket=PORT or --tcp=PORT: use a socket connecting on the specified port for communication

Installing

You can run dub fetch dls and then dub run dls:bootstrap to install dls. The second command will output a path that will point to the DLS executable. DLS will automatically update itself whenever a new version is out.

Client side configuration

All these keys should be formatted as d.dls.[section].[key] (e.g. d.dls.format.endOfLine).

Server initialization options

DLS supports a few custom initialization options in the InitializeParams.initializationOptions object sent with the initialize request:

interface InitializationOptions: {
    autoUpdate?: boolean = true;
    preReleaseBuilds?: boolean = false;
    catchErrors?: boolean = false;
    logFile?: string = "";
    capabilities?: {
        hover?: boolean = true;
        completion?: boolean = true;
        definition?: boolean = true;
        typeDefinition?: boolean = true;
        references?: boolean = true;
        documentHighlight?: boolean = true;
        documentSymbol?: boolean = true;
        workspaceSymbol?: boolean = true;
        codeAction?: boolean = true;
        documentFormatting?: boolean = true;
        documentRangeFormatting?: boolean = true;
        documentOnTypeFormatting?: boolean = true;
        rename?: boolean = true;
    }
}

Caveats

The server may delegate a few operations to the client-side extension depending on the language client's capabilities. The client should watch these files for the server to work properly:

• dub.selections.json
• dub.json
• dub.sdl
• *.ini

If the client supports dynamic registration of the workspace/didChangeWatchedFiles method, then the server will automatically register file watching. If the client doesn't support dynamic registration however, the client-side extension will need to manually do it. The server needs to know at least when dub.selections.json files change to properly provide completion support. If dub.json and dub.sdl are also watched, dub.selections.json can be regenerated on demand. Watching *.ini allows DLS to monitor D-Scanner config files, even if the name is changed in the config and isn't dscanner.ini.

Custom messages

Since the LSP defines messages with methods starting in $/ to be implementation dependant, DLS uses $/dls as a prefix for custom messages.

interface TranslationParams {
    tr: string;
}

interface DlsUpgradeSizeParams extends TranslationParams {
    size: number;
}

Contributing

Translations

The file i18n/data/translations.json contains localization strings. Adding new strings is straightforward, simply add new entries in the message objects with the locale identifier as key and the translated string as value.

Which branch should be targeted by pull requests ?

Is it work on an upcoming new feature ? Then the master branch should be targeted. Is it a fix for a bug you've encountered ? Then the latest release/v[MAJOR].[MINOR].x branch should be targeted.