lsp, lsp-types 1.2.0.0

lsp-types 1.2.0.0

• Prevent crashing when optional fields are missing (@anka-213)
• Use StrictData (@wz1000)
• Add MarkupContent in SignatureHelp types (@michaelpj)
• Add activeParameter support in SignatureInformation (@michaelpj)
• Add label offset support in SignatureHelp (@michaelpj)
• Add some documentation comments to SignatureHelp types (@michaelpj)
• Add support for InsertReplaceEdit (@michaelpj)
• Add support for InsertTextMode (@michaelpj)
• Add resolveSupport (@michaelpj)
• Fix applying a TextEdit past the end of the document (#271) (@michaelpj)
• Use Empty instead of () as progress create response (#295) (@wz1000)
• Add tag support for DocumentSymbol, SymbolInformation, and document symbol provider label (#301) (@michaelpj)
• Support change annotations (#302) (@michaelpj)
• Add some more missing lenses (#307) (@michaelpj)

lsp 1.2.0.0

• Parse config from initializeOptions and pass in the old value of config to onConfigurationChange (#285) (wz1000)
• Break up big TVar record into lots of small TVars (#286) (@wz1000)
• Add some INLINE pragmas (@wz1000)
• Make method equality work for CustomMethods (@wz1000)

lsp-test 0.14.0.0

• Update for lsp-types-1.2 (@wz1000)
• Limit diagnostics by range in getCodeActions (@aufarg)
• Kill timeout thread to avoid building up thousands of old TimeoutMessages (@wz1000)

1.1.1.0

• Don't send begin progress notification twice (@wz1000)

1.1.0.0

• Fix prepareRename reponse and prepareProvider (@kirelagin)
• Fix deriving instance of MonadUnliftIO (@banacorn)
• Add support for file and folder operations in WorkspaceEdit (@banacorn)
  Instead of having TextDocumentEdit in WorkspaceEdit

data WorkspaceEdit =
  WorkspaceEdit
    { _changes         :: Maybe WorkspaceEditMap
    , _documentChanges :: Maybe (List TextDocumentEdit)
    } deriving (Show, Read, Eq)

It is now replaced by a new type called DocumentChange

data WorkspaceEdit =
  WorkspaceEdit
    { _changes         :: Maybe WorkspaceEditMap
    , _documentChanges :: Maybe (List DocumentChange)
    } deriving (Show, Read, Eq)

Which is just a synonym of union of WorkspaceEdit and other operations

type DocumentChange = TextDocumentEdit |? CreateFile |? RenameFile |? DeleteFile

• Add new CodeAction features (isPreferred, disabled) (@pepeiborra)
• Respond to requests with missing handlers (@wz1000)
• Use Text over String in more places (@wz1000)
• Add missing lenses (@wz1000, @bubba)

1.0.0.1

This contains fixes for building on GHC 8.4.4

1.0.0.0

1.0.0.0 is a major rework with both internal and external facing changes, and
will require manual migration.

• The package has been renamed from haskell-lsp to lsp, and similarly for haskell-lsp-types to lsp-types
  • Because of this, all modules are now exported from Language.LSP.X rather than Language.Haskell.X.
• Both lsp and lsp-types have been reworked to be much more type safe
• The 3.15 specification should be fully supported now. If you find anything in
  the specification that isn't in lsp-types, please let us know
• The Capture module has been removed as it will be reworked later on and moved to lsp-test
• lsp can now handle dynamic registration through the registerCapability and
  unregisterCapability functions

Type safety

There are three types of concrete messages, NotificationMessage,
RequestMessage and ResponseMessage. They are parameterised by their
Method, which determines what type their parameters or response result must be.

data RequestMessage (m :: Method f Request) = RequestMessage
    { _jsonrpc :: Text
    , _id      :: LspId m
    , _method  :: SMethod m
    , _params  :: MessageParams m
    }

A Method in turn is parameterised by whether it originates from the client or
the server, and whether it is used for notifications or requests:

TextDocumentFoldingRange           :: Method FromClient Request
TextDocumentSelectionRange         :: Method FromClient Request
WindowShowMessage                  :: Method FromServer Notification
WindowShowMessageRequest           :: Method FromServer Request

Each Method also has a singleton counterpart which allows it to be used at the
term level, for example in RequestMessage._method:

STextDocumentFoldingRange           :: SMethod TextDocumentFoldingRange
STextDocumentSelectionRange         :: SMethod TextDocumentSelectionRange

SWindowShowMessage                  :: SMethod WindowShowMessage
SWindowShowMessageRequest           :: SMethod WindowShowMessageRequest

The type families MessageParams and ResponseResult map each Method to the
appropriate type to be used in a response:

ResponseResult TextDocumentRename            = WorkspaceEdit
ResponseResult TextDocumentPrepareRename     = Range |? RangeWithPlaceholder

Also new is the |? type which represents union types in
TypeScript,
and is used throughout the specification where a field can accept several
different types.

As an example of this in action, the types of your handlers will now depend on
whether or not they are a request or a notification. They will pass along the
precise type for the parameters the method you are handling, and in the case of
a request handler, will expect that the response you give back is of the correct
type as well.

type family Handler (f :: Type -> Type) (m :: Method from t) = (result :: Type) | result -> f t m where
  Handler f (m :: Method _from Request)      = RequestMessage m -> (Either ResponseError (ResponseResult m) -> f ()) -> f ()
  Handler f (m :: Method _from Notification) = NotificationMessage m -> f ()

LspT

LspFuncs has been removed and instead functionality is exposed through
functions in the MonadLsp class.

getVirtualFile :: MonadLsp config m => NormalizedUri -> m (Maybe VirtualFile)
sendRequest :: forall (m :: Method FromServer Request) f config. MonadLsp config f
            => SServerMethod m
            -> MessageParams m
            -> (Either ResponseError (ResponseResult m) -> f ())
            -> f (LspId m)

It is parameterised over the server's LSP configuration type and the underlying
monad.
We recommend that you build your own monad for your server on top of the LspT
transformer, so it will automatically become an instance of MonadLsp.

Inside the new ServerDefinition data type which gets passed to runServer,
you need to specify how to convert from IO to your monad and back in
interpretHandler so that lsp can execute your monad inside the handlers. You
can use the result returned from doInitialize to pass along the
LanguageContextEnv needed to run an LspT, as well as anything else your
monad needs.

type 
ServerDefinition { ...
, doInitialize = \env _req -> pure $ Right env
, interpretHandler = \env -> Iso 
   (runLspT env) -- how to convert from IO ~> m
   liftIO        -- how to convert from m ~> IO
}

Steps to migrate

1. In your .cabal file change any haskell-lsp dependencies to lsp
2. Replace your existing imports with Haskell.LSP.Server
3. If necessary define your own monad and fill in interpretHandler
4. Migrate your handlers to use notificationHandler and requestHandler,
   passing along the corresponding SMethod (See example/Simple.hs)
5. Remove any storage/use of LspFuncs and instead call the corresponding
   functions directly from your monad instead of IO

0.23.0.0

• Add runWith for transporots other than stdio (@paulyoung)
• Fix race condition in event captures (@bgamari)
• Tweak the sectionSeparator (@alanz)
• Add hashWithSaltInstances (@ndmitchell)
• Fix CompletionItem.tags not being optional (@bubba)
• Avoid unnecessary normalisation in Binary instance for
  NormalizedFilePath (@cocreature)
• Fix ordering of TH splices (@fendor)

0.22.0.0

• ResponseMessage results are now an Either type (@greenhat)
• Support for GHC 8.10.1

0.21.0.0

• Stop getCompletionPrefix from crashing if beforePos is empty
• Add DidChangeWatchedFilesRegistrationOptions
• Add NormalizedFilePath from ghcide
• Add diagnostic and completion tags
• Fix language server example
• Correctly fix the problem with '$/' notifications
• Add azure ci

0.17.0.0

• Update progress reporting to match the LSP 3.15 specification (@cocreature)
• Fix progress cancellation action being retained (@mpickering)
• Respect both codeActionProvider and codeActionHandler in server capabilities (@fendor)
• Ensure ResponseMessage has either a result or an error (@cocreature)