mirror of
https://github.com/enso-org/enso.git
synced 2024-12-18 12:31:42 +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). |
||
|---|---|---|
| .. | ||
| debugger | ||
| distribution | ||
| flexer | ||
| infrastructure | ||
| language-server | ||
| libraries | ||
| parser | ||
| polyglot | ||
| rfcs | ||
| runtime | ||
| security | ||
| semantics | ||
| style-guide | ||
| syntax | ||
| types | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| enso-philosophy.md | ||
| getting-enso.md | ||
| graalvm-m1-mac.md | ||
| README.md | ||
| runtime-guide.md | ||
| runtime-roadmap.md | ||
| SECURITY.md | ||
| layout | title | category | tags | order | ||
|---|---|---|---|---|---|---|
| docs-index | Enso Engine Developer Documentation | summary |
|
0 |
Enso Engine Developer Documentation
This folder contains the documentation for the implementation of the Enso programming language. The documentation is broken up by subject, within the below-listed categories, and each subject combines information about the design, specification, and implementation of the feature to which it pertains.
We provide a number of useful resources for getting a quick understanding of the Enso project:
- The Enso Philosophy: Information on the design philosophy behind Enso, and why we build things in the way we do.
- Contributing Guidelines: Information for people wanting to contribute to Enso (in many different ways).
- Community Code of Conduct: The code of conduct for members of our community, developers and users alike.
- Security Guidelines: Security guidelines for the Enso project, including supported versions and our vulnerability reporting process.
- Getting Enso: Instructions for how to get and run a copy of Enso.
- Runtime Roadmap: An analysis of the pressing changes that should be made to the runtime.
- Runtime Guide: A tour of the runtime, and some pointers as to useful resources.
It is broken up into categories as follows:
- Distribution: Information on how we distribute Enso to our users, and how Enso packages themselves work.
- Language Server: Information on the Enso language server, its protocol, and how it integrates with the runtime.
- Polyglot: Information on Enso's polyglot functionality, and how it is integrated into the surface Enso language.
- RFCs: RFCs for Enso's development and evolution.
- Runtime: Specification and documentation of the way that the Enso runtime is designed and implemented.
- Semantics: A specification of Enso's semantics.
- Style Guides: Style guides for the code written as part of the Enso project.
- Syntax: A specification of Enso's syntax.
- Types: A specification of Enso's type system and type theory.
- Debugger: A specification of Enso's debugger.
- Parser: Design and specification of the Enso parser.
- Infrastructure: Description of the infrastructure for building Enso.
- Libraries: Description of Enso's Library Ecosystem.