mirror of
https://github.com/enso-org/enso.git
synced 2024-12-18 22:21:48 +03:00
c6835d2de7
Show custom icons in Component Browser for entries that have a non-empty `Icon` section in their docs with the section's body containing a name of a predefined icon. https://www.pivotaltracker.com/story/show/182584336 #### Visuals A screenshot of a couple custom icons in the Component Browser: <img width="346" alt="Screenshot 2022-07-27 at 15 55 33" src="https://user-images.githubusercontent.com/273837/181265249-d57f861f-8095-4933-9ef6-e62644e11da3.png"> # Important Notes - The PR assigns icon names to four items in the standard library, but only three of them are shown in the Component Browser because of [a parsing bug in the Engine](https://www.pivotaltracker.com/story/show/182781673). - Icon names are assigned only to four items in the standard library because only two currently predefined icons match entries in the currently defined Virtual Component Groups. Adjusting the definitions of icons and Virtual Component Groups is covered by [a different task](https://www.pivotaltracker.com/story/show/182584311). - A bug in the documentation of the Enso protocol message `DocSection` is fixed. A `text` field in the `Tag` interface is renamed to `body` (this is the field name used in Engine). |
||
|---|---|---|
| .. | ||
| language-server-http-endpoints.md | ||
| protocol-architecture.md | ||
| protocol-common.md | ||
| protocol-language-server.md | ||
| protocol-project-manager.md | ||
| README.md | ||
| streaming-file-transfer.md | ||
| layout | title | category | tags | order | ||
|---|---|---|---|---|---|---|
| section-summary | Language Server | language-server |
|
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 Enso Protocol Architecture: The architecture of the Enso protocol.
- Streaming File Transfer: Documentation on how the streaming file transfer mechanism works.
The protocol messages are broken up into documents as follows:
- Common Message Specification: The common messages and types
- Project Manager Message Specification: The messages and types pertaining to the project manager component.
- Language Server Message Specification: The messages and types pertaining to the language server component.
- Language Server Http Endpoints Specification Specification of the Language Server Http endpoints.