mirror of
https://github.com/enso-org/enso.git
synced 2024-12-24 14:24:11 +03:00
2f9e7f51af
In the current workflow, at first, the default Unnamed project is created, and the Suggestions database is populated with entries from the Unnamed.* modules. When the user changes the name of the project, we should update all modules in the Suggestion Database with the new project name. This PR implements module renaming in the Suggestions database and fixes the initialization issues. - add: search/invalidateSuggestionsDatabase JSON-RPC command that resets the corrupted Suggestions database - update: SuggestionsHandler to rename the modules in the SuggestionsDatabase when the project is renamed - fix: MainModule initialization |
||
|---|---|---|
| .. | ||
| 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.