Hubert Plociniczak a11bddcb74 Inline execution should support FQNs (#8454) ... * Test illustrating problems with FQNs Inline execution fails with `Compile error: The name `Standard` could not be found.`. * Ensure InlineContext carries Package Repos info Previously, there was no requirement that inline execution should allow for FQNs. This meant that the omission of Package Repository info went unnoticed. In order to be able to refer to `Standard.Visualization.Preprocessor` it has to be exported as well.		2023-12-06 10:03:06 +01:00
..
bin	Upgrade enso to GraalVM for jdk 21 (#7991)	2023-11-17 18:02:36 +00:00
engine/THIRD-PARTY	Add graalpy packages to the component directory (#8351)	2023-12-04 11:50:59 +00:00
launcher	Upgrade enso to GraalVM for jdk 21 (#7991)	2023-11-17 18:02:36 +00:00
lib/Standard	Inline execution should support FQNs (#8454)	2023-12-06 10:03:06 +01:00
project-manager/THIRD-PARTY	Upgrade enso to GraalVM for jdk 21 (#7991)	2023-11-17 18:02:36 +00:00
enso.bundle.template	Better component handling in the project manager (#1399)	2021-01-15 15:26:51 +00:00
launcher-manifest.yaml	Bump the development version number (#1389)	2021-01-06 08:57:02 +00:00
manifest.template.yaml	Upgrade enso to GraalVM for jdk 21 (#7991)	2023-11-17 18:02:36 +00:00