Hybrid visual and textual functional programming.
Go to file
Radosław Waśko df4a7efcdd
Add AWS SSO JARs to the Standard.AWS library (#9782)
As reported by our users, when using the AWS SSO, our code was failing with:
```
Execution finished with an error: To use Sso related properties in the 'xyz' profile, the 'sso' service module must be on the class path.
```

This PR adds the missing JARs to fix that.

Additionally it improves the license review tool UX a bit (parts of #9122):
- sorting the report by amount of problems, so that dependencies with unresolved problems appear at the top,
- semi-automatic helper button to rename package configurations after a version bump,
- button to remove stale entries from config (files or copyrights that disappeared after update),
- button to add custom copyright notice text straight from the report UI,
- button to set a file as the license for the project (creating the `custom-license` file automatically)
- ability to filter processed projects - e.g. `openLegalReviewReport AWS` will only run on the AWS subproject - saving time processing unchanged dependencies,
- updated the license search heuristic, fixing a problem with duplicates:
- if we had dependencies `netty-http` and `netty-http2`, because of a prefix-check logic, the notices for `netty-http` would also appear again for `netty-http2`, which is not valid. I have improved the heuristic to avoid these false positives and removed them from the current report.
- WIP: button to mark a license type as reviewed (not finished in this PR).
2024-04-25 18:44:51 +00:00
.cargo Bump rustc to nightly-2023-01-12 (#4053) 2023-02-02 23:05:25 +00:00
.github [CI] Provide latest FlatBuffers to the Engine build. (#9654) 2024-04-12 10:10:44 +00:00
.vscode Make conversion of double to BigDecimal exact (#9740) 2024-04-25 11:22:50 +00:00
actions/setup-build misc: bump wasm-pack (#3983) 2022-12-14 18:45:39 +01:00
app Node creation improvements (#9781) 2024-04-25 09:18:38 -04:00
build [CI] Provide latest FlatBuffers to the Engine build. (#9654) 2024-04-12 10:10:44 +00:00
distribution Add AWS SSO JARs to the Standard.AWS library (#9782) 2024-04-25 18:44:51 +00:00
docs In-memory suggestions (#9751) 2024-04-22 11:02:17 +00:00
engine Make conversion of double to BigDecimal exact (#9740) 2024-04-25 11:22:50 +00:00
lib Towards simplifying runtime-compiler dependencies (#8894) 2024-04-25 10:03:42 +02:00
project Add AWS SSO JARs to the Standard.AWS library (#9782) 2024-04-25 18:44:51 +00:00
std-bits Make conversion of double to BigDecimal exact (#9740) 2024-04-25 11:22:50 +00:00
test Add AWS SSO JARs to the Standard.AWS library (#9782) 2024-04-25 18:44:51 +00:00
tools Add AWS SSO JARs to the Standard.AWS library (#9782) 2024-04-25 18:44:51 +00:00
.envrc Google Analytics events for opening and closing the app, and opening and closing projects (#9779) 2024-04-25 11:33:59 +00:00
.git-blame-ignore-revs More E2E tests; export default classes from modules (#8730) 2024-01-31 11:35:41 +00:00
.gitattributes Eliminate VCS TimeoutExceptions on startup (#8080) 2023-10-18 09:34:08 +00:00
.gitignore Google Analytics events for opening and closing the app, and opening and closing projects (#9779) 2024-04-25 11:33:59 +00:00
.ignore Refactoring: merge utils into prelude; merge workspaces. (#3151) 2021-11-10 14:36:08 +01:00
.jvmopts Update java formatter sbt plugin (#8543) 2023-12-15 14:45:23 +00:00
.node-version Vue dependency update, better selection performance, visible quotes in text inputs (#9204) 2024-03-06 15:34:07 +00:00
.prettierignore Syntactic synchronization, automatic parentheses, metadata in Ast (#8893) 2024-02-02 10:22:18 +01:00
.prettierrc.yaml Fix prettier config; run prettier (#6132) 2023-03-31 14:49:34 +02:00
.scalafmt.conf Bump SBT and Scalafmt (#1203) 2020-10-22 16:12:28 +02:00
build-config.yaml [CI] Provide latest FlatBuffers to the Engine build. (#9654) 2024-04-12 10:10:44 +00:00
build.sbt Add AWS SSO JARs to the Standard.AWS library (#9782) 2024-04-25 18:44:51 +00:00
Cargo.lock Reduce parser dependencies (#9671) 2024-04-11 00:27:19 -04:00
Cargo.toml Reduce parser dependencies (#9671) 2024-04-11 00:27:19 -04:00
CHANGELOG.md Writing to Data Links (#9750) 2024-04-25 17:55:49 +00:00
clippy.toml Build script merge (#3743) 2022-10-10 23:38:48 +02:00
flake.lock Google Analytics events for opening and closing the app, and opening and closing projects (#9779) 2024-04-25 11:33:59 +00:00
flake.nix Google Analytics events for opening and closing the app, and opening and closing projects (#9779) 2024-04-25 11:33:59 +00:00
LICENSE Set up the repository (#1) 2019-06-11 17:07:54 +01:00
package-lock.json Automatic reconnect with Language Server. (#9691) 2024-04-19 13:39:45 +00:00
package.json Remove ensogl-pack (#9407) 2024-03-18 12:18:18 +00:00
README.md Consistent naming of visualization (#7124) 2023-06-26 17:04:35 +00:00
RELEASES.md Add API for component groups (#3286) 2022-02-24 15:41:14 +03:00
run Build script: git-clean and cwd fixes (#8424) 2023-11-29 20:35:06 +01:00
run.cmd Build script fixes & improvements (#8285) 2023-11-23 21:19:31 +01:00
run.ps1 Build script fixes & improvements (#8285) 2023-11-23 21:19:31 +01:00
rust-toolchain.toml Bump Rust Toolchain (#9517) 2024-03-24 23:45:55 +00:00
rustfmt.toml remove unused rust modules (#9540) 2024-03-27 12:19:38 +00:00
vitest.workspace.ts Fix AST spacing (#9366) 2024-03-12 01:57:29 +00:00

Chat Actions Status Actions Status License License


Enso.org. Get insights you can rely on. In real time.

Enso is an award-winning interactive programming language with dual visual and textual representations. It is a tool that spans the entire stack, going from high-level visualization and communication to the nitty-gritty of backend services, all in a single language. Watch the following introduction video to learn what Enso is, and how it helps companies build data workflows in minutes instead of weeks.


Screenshot 2021-04-15 at 12 16 32

Enso's Features

Turning your data into knowledge is slow and error-prone. You cant trust tools that dont embrace best practices and provide quality assurance. Enso redefines the way you can work with your data: it is interactive, provides intelligent assistance, and was designed on a strong mathematical foundation, so you can always trust the results you get.

      Intelligent suggestions of possible next steps. Build workflows in minutes instead of weeks.
      Enso analyses the data, suggests possible next steps, and displays related help and examples. It lets you build dashboards, RPA workflows, and apps, with no coding required. Enso ships with a robust set of libraries, allowing you to work with local files, databases, HTTP services, and other applications in a seamless fashion.
      Learn more →
      Reproducible, trustworthy results.
      Versioning and visual data quality management allow you to trust the results that you get.
      Learn more →
      A powerful, purely functional language. Both visual and textual.
      Enso incorporates many recent innovations in data processing and programming language design to allow you to work interactively and trust the results that you get. It is a purely functional programming language with higher-order functions, user-defined algebraic datatypes, pattern-matching, and two equivalent representations that you can switch between on-demand.
      Learn more →
      Mix languages with close-to-zero interop overhead.
      Import any library from Enso, Java, JavaScript, R, or Python, and use functions, callbacks, and data types without any wrappers. Enso uses GraalVM to compile them to the same instruction set with a unified memory model.
      Learn more →
      A cutting-edge visualization engine.
      Enso is equipped with a highly-tailored WebGL visualization engine capable of displaying many millions of data points at 60 frames per second in a web browser. Currently, Enso includes a set of core data visualizations out of the box, and you can easily extend it with libraries such as D3.js, Three.js, Babylon.js, deck.gl, VTK.js, Potree, and many more.
      Learn more →
      Runs everywhere.
      Enso is available on macOS, Windows, and GNU/Linux, and the Enso IDE runs on web-native technologies. In time, you'll be able to run it in the web-browser, giving even your tablet and phone access to your data.
      Learn more →

Getting Started

An example Enso graph



Enso Source Code

If you want to start using Enso, please see the download links in the getting started section above. Alternatively, you can get the IDE here. This section is intended for people interested in contributing to the development of Enso.

Enso is a community-driven open source project which is, and will always be, open and free to use. Join us, help us to build it, and spread the word!


Project Components

Enso consists of several sub projects:

  • Enso Engine: The Enso Engine is the set of tools that implement the Enso language and its associated services. These include the Enso interpreter, a just-in-time compiler and runtime (both powered by GraalVM), and a language server that lets you inspect Enso code as it runs. These components can be used on their own as command line tools.

  • Enso IDE: The Enso IDE is a desktop application that allows working with the visual form of Enso. It consists of an Electron application, a high performance WebGL UI framework, and the searcher which provides contextual search, hints, and documentation for all of Enso's functionality.


License

The Enso Engine is licensed under the Apache 2.0, as specified in the LICENSE file. The Enso IDE is licensed under the AGPL 3.0, as specified in the LICENSE file.

This license set was chosen to provide you with complete freedom to use Enso, create libraries, and release them under any license of your choice, while also allowing us to release commercial products on top of the platform, including Enso Cloud and Enso Enterprise server managers.


Contributing to Enso

Enso is a community-driven open source project which is and will always be open and free to use. We are committed to a fully transparent development process and highly appreciate every contribution. If you love the vision behind Enso and you want to redefine the data processing world, join us and help us track down bugs, implement new features, improve the documentation or spread the word!

If you'd like to help us make this vision a reality, please feel free to join our chat, and take a look at our development and contribution guidelines. The latter describes all the ways in which you can help out with the project, as well as provides detailed instructions for building and hacking on Enso.

If you believe that you have found a security vulnerability in Enso, or that you have a bug report that poses a security risk to Enso's users, please take a look at our security guidelines for a course of action.


Enso's Design

If you would like to gain a better understanding of the principles on which Enso is based, or just delve into the why's and what's of Enso's design, please take a look in the docs/ folder. It is split up into subfolders for each component of Enso. You can view this same documentation in a rendered form at the developer docs website.

This folder also contains a document on Enso's design philosophy, that details the thought process that we use when contemplating changes or additions to the language.

This documentation will evolve as Enso does, both to help newcomers to the project understand the reasoning behind the code, and also to act as a record of the decisions that have been made through Enso's evolution.