Repository navigation
Conversation
A manifest can now list other projects as dependencies, by a path to their manifest that may lead outside the project. Their network definitions, network sets and sub-networks are referred to by qualified names such as `ea::river`, and their models can be the networks of a multi-model. Dependencies load transitively, a project reached by several routes is loaded once, and cycles are reported. An optional SHA-256 hash pins a dependency's manifest, and a `DependencyPolicy` in the new `ResolveOptions` can deny dependencies or confine them to a directory. A project's `exports` limit what others may use from it. Problems found inside a dependency are reported as being in it, and a dependency's set limits apply only to the sets that are selected from. Relative data paths in a dependency's files are rebased onto the root project, and provenance records the dependency each component came from. The example's neighbouring network is now a separate project, which reads its demand from a CSV file of its own.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A manifest can now list other projects as dependencies, by a path to their manifest that may lead outside the project. Their network definitions, network sets and sub-networks are referred to by qualified names such as
ea::river, and their models can be the networks of a multi-model. Dependencies load transitively, a project reached by several routes is loaded once, and cycles are reported. An optional SHA-256 hash pins a dependency's manifest, and aDependencyPolicyin the newResolveOptionscan deny dependencies or confine them to a directory.A project's
exportslimit what others may use from it. Problems found inside a dependency are reported as being in it, and a dependency's set limits apply only to the sets that are selected from. Relative data paths in a dependency's files are rebased onto the root project, and provenance records the dependency each component came from.The example's neighbouring network is now a separate project, which reads its demand from a CSV file of its own.