sbt.internal.bsp

An optional request id to know the origin of this report.

A status code for the execution.

Command arguments runnable via system processes to start a BSP server

The bsp version of the build tool

A collection of languages supported by this BSP server

The name of the build tool

The version of the build tool

The languages that this client supports. The ID strings for each language is defined in the LSP. The server must never respond with build targets for other languages than those that appear in this list.

Reloading the workspace state through workspace/reload is supported

The languages the server supports compilation via method buildTarget/compile.

The server provides sources for library dependencies via method buildTarget/dependencySources

The languages the server supports test execution via method buildTarget/test

The directory where this target belongs to. Multiple build targets are allowed to map to the same base directory, and a build target is not required to have a base directory. A base directory does not determine the sources of a target, see buildTarget/sources.

The capabilities of this build target.

Language-specific metadata about this target. See ScalaBuildTarget as an example.

Kind of data to expect in the data field. If this field is not set, the kind of data is not specified.

The direct upstream build target dependencies of this build target

A human readable name for this target. May be presented in the user interface. Should be unique if possible. The id.uri is used if None.

The target’s unique identifier

The set of languages that this target contains. The ID string for each language is defined in the LSP.

Free-form string tags to categorize or label this build target. For example, can be used by the client to: - customize how the target should be translated into the client's project model. - group together different but related targets in the user interface. - display icons or colors in the user interface. Pre-defined tags are listed in BuildTargetTag but clients and servers are free to define new tags for custom purposes.

This target can be compiled by the BSP server.

This target can be debugged by the BSP server.

This target can be run by the BSP server.

This target can be tested by the BSP server.

The target's Uri

A sequence of build targets to clean

Indicates whether the clean cache request was performed or not

Optional message to display to the user

Optional arguments to the compilation process

An optional unique identifier generated by the client to identify this request. The server may include this id in triggered notifications or response.

A sequence of build targets to compile

The total number of reported errors compiling this target.

An optional request id to know the origin of this report

The build target that was compiled

The total number of milliseconds it took to compile the target.

The total number of reported warnings compiling the target.

The target's Uri

A language-agnostic JSON object interpreted by the server.

The kind of data to expect in the data field.

A sequence of build targets affected by the debugging action.

List of resources containing source files of the target's dependencies. Can be source files, jar files, zip files, or directories

The diagnostic's code. Can be omitted.

The diagnostic's message.

The range at which the message applies.

The diagnostic's severity. Can be omitted. If omitted it is up to the client to interpret diagnostics as error, warning, info or hint.

A human-readable string describing the source of this diagnostic, e.g. 'typescript' or 'super lint'.

The BSP version that the client speaks

The capabilities of the client

Additional metadata about the client

Name of the client

The rootUri of the workspace

The version of the client

The BSP version that the server speaks

The capabilities of the build server

Additional metadata about the server

Name of the server

The version of the server

The semanticdb plugin version that should be enabled for Metals code navigation

The list of scala versions that are supported by Metals

Character offset on a line in a document (zero-based).

Line position in a document (zero-based).

The build target where the diagnostics origin. It is valid for one text to belong to multiple build targets, for example sources that are compiled against multiple platforms (JVM, JavaScript).

The diagnostics to be published by the client

The request id that originated this notification

Whether the client should clear the previous diagnostics mapped to the same textDocument and buildTarget

The document where the diagnostics are published.

The range's end position.

The range's start position.

List of resource files.

Optional arguments to the executed application.

Language-specific metadata for this execution.

Kind of data to expect in the data field. If this field is not set, the kind of data is not specified.

An option identifier gnerated by the client to identify this request. The server may include this id in triggered notifications or responses.

The build target to run.

An optional request id to know the origin of this report.

A status code for the execution.

A sequence of Scala imports that are automatically imported in the sbt build files.

The inverse of parent, list of targets that have this build target defined as their parent. It can contain normal project targets or sbt build targets if this target represents an sbt meta-meta build.

An optional parent if the target has an sbt meta project.

The sbt version. Useful to support version-dependent syntax.

The Scala build target describing the scala version and scala jars used by this sbt version.

A sequence of Scala jars such as scala-library, scala-compiler and scala-reflect.

The target platform for this target

The binary version of scalaVersion. For example, 2.12 if scalaVersion is 2.12.4.

The Scala organization that is used for a target.

The scala version to compile this target

The user arguments to the main entrypoint.

The main class to run.

Additional environment variables for the application.

The jvm options for the application.

The main class items

The build target that contains the test classes.

An optional number uniquely identifying a client request.

An optional id of the request that triggered this result.

The fully qualified names of the test classes in this target

The name of the test framework used in test classes.

The build target that contains the test classes.

An optional number uniquely identifying a client request.

An optional id of the request that triggered this result.

The output directory for classfiles produced by this target

The dependency classpath for this target, must be identical to what is passed as arguments to the -classpath flag in the command line interface of scalac.

Additional arguments to the compiler. For example, -deprecation.

Indicates if this source is automatically generated by the build and is not intended to be manually edited by the user.

Type of file of the source item, such as whether it is file or directory.

Either a text document or a directory. A directory entry must end with a forward slash "/" and a directory entry implies that every nested text document within the directory belongs to this source item.

The text documents or and directories that belong to this build target.

Optional metadata about the task.

Kind of data to expect in the data field.

Optional timestamp of when the event started in milliseconds since Epoch.

Optional message describing the task.

Task completion status: 1 -> success, 2 -> error, 3 -> cancelled

Unique id of the task with optional reference to parent task id.

A unique identifier

The parent task ids, if any. A non-empty parents field means this task is a sub-task of every parent task.

Optional metadata about the task.

Kind of data to expect in the data field.

Optional timestamp of when the event started in milliseconds since Epoch.

Message describing the task progress.

If known, completed amount of work units in this task.

Unique id of the task with optional reference to parent task id.

If known, total amount of work units in this task.

Name of a work unit. For example, "files" or "tests". May be empty.

Optional metadata about the task.

Kind of data to expect in the data field.

Optional timestamp of when the event started in milliseconds since Epoch.

Optional message describing the task.

Unique id of the task with optional reference to parent task id.

Optional arguments to the test execution engine.

Language-specific metadata for this test execution.

Kind of data to expect in the data field. If this field is not set, the kind of data is not specified.

An option identifier generated by the client to identify this request. The server may include this id in triggered notifications or responses.

A sequence of build targets to test.

An optional request id to know the origin of this report.

A status code for the execution.

The file's Uri

The build targets in this workspace that contain sources with the given language ids.