enso/docs/language-server
Dmitry Bushev a6b2415188
Add JSON-RPC Timeout Error (#1332)
Add a separate timeout error to distinguish between
the request timeouts and other service errors.
2020-12-09 15:53:00 +03:00
..
protocol-architecture.md Update Project Manager Protocol (#1240) 2020-11-02 09:58:33 +01:00
protocol-common.md Add JSON-RPC Timeout Error (#1332) 2020-12-09 15:53:00 +03:00
protocol-language-server.md Forking Language Server in the Project Manager (#1305) 2020-12-02 16:56:47 +01:00
protocol-project-manager.md Forking Language Server in the Project Manager (#1305) 2020-12-02 16:56:47 +01:00
README.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00

layout title category tags order
section-summary Language Server language-server
language-server
readme
0

Language Server

The Enso Language Server is responsible for providing language services to the Enso IDE (and other clients). This mainly involves speaking the Enso protocol and orchestrating the runtime in response to this. It is responsible for:

  • Introspection Services: Giving clients the ability to observe information about their running code including values, types, profiling information, and debugging.
  • Code Execution: The ability for clients to execute arbitrary Enso code in arbitrary scopes. This can be used in conjunction with the above to provide a REPL with an integrated debugger.
  • Code Completion: Sophisticated completion functionality that refines suggestions intelligently based on context.
  • Node Management: Tracking and providing the language server's internal node representation of the Enso program.
  • Code Analysis: Analysis functionality for Enso code (e.g. find usages, jump-to-definition, and so on).
  • Refactoring: Refactoring functionality for Enso code (e.g. rename, move, extract, and so on).
  • Type Interactions: Features for type-driven-development that allow users to interact with the types of their programs.

This folder contains all documentation pertaining to the Language Server, which is broken up as follows:

The protocol messages are broken up into documents as follows: