mirror of
https://github.com/enso-org/enso.git
synced 2024-11-29 17:22:57 +03:00
e585904291
* Mitiigate LS DDOS scenario on startup For a medium-size project with a lot of visualizations, Language Server will be flooded with visualization requests on startup. Due to an existing limit for the job execution engine, some of those requests might have been silently dropped. This change lifts that limit until a better fix can be invented. Additionally, a slow startup might lead to a timeout when serving open file request. This change adds some retries as a fallback mechanism/progress monitoring. * add runtime-fat-jar to a list of aggregates |
||
|---|---|---|
| .. | ||
| src | ||
| README.md | ||
Enso Language Server
The Enso Language Server is responsibile for providing a remote-communication protocol for the runtime, exposing many of its features to the users. In addition it provides the backing service for much of the IDE functionality associated with the language. It encompasses the following functionality:
- 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.