Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new interface with support for imports (
analyzeSourceCodeDir
) for analyzing multiple files.Import Definition
In EO, imports refer to the following constructs at the top of the file:
+alias bndAlias pkgName.bndSrc
Each import consists of three parts:
bndAlias
(binding name can be changed when its imported);pkgName
(packageless objects are stored are a part of the global package with no name);bndSrc
(can be either a top-level object or a path to some nested binding).Supported Functionality
The following import functionality is currently supported:
Importing of packageless bindings
+alias objName
+alias objName.pathToNestedBnd
Importing of bindings with package
+alias pkgName.srcPath
Aliasing in Imports
+alias name pkgName.srcPath
Sharing of top-level objects within the same package
File1:
File2:
Unsupported Features
The following is NOT supported:
Notice how object
a
is also added to File3File1: