-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add support for YAML and TOML scenario definitions (#176)
- Loading branch information
Showing
20 changed files
with
958 additions
and
74 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
File renamed without changes.
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
name = "example-toml" | ||
description = "This is an example scenario written in TOML, in which the user depends on a single package `a` which requires `b`." | ||
|
||
[expected] | ||
satisfiable = true | ||
explanation = "The latest valid version of `b` should be installed. `b==3.0.0` is not valid because it requires `c` which does not exist." | ||
|
||
[expected.packages] | ||
a = "1.0.0" | ||
b = "2.0.0" | ||
|
||
[root] | ||
requires = [ "a" ] | ||
|
||
[packages.a.versions."1.0.0"] | ||
requires = [ "b>1.0.0" ] | ||
|
||
[packages.b.versions] | ||
"1.0.0" = { } | ||
"2.0.0" = { } | ||
|
||
[packages.b.versions."3.0.0"] | ||
requires = [ "c" ] |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
- name: example-yaml | ||
description: This is an example scenario written in YAML, in which the user depends on a single | ||
package `a` which requires `b`. | ||
expected: | ||
satisfiable: true | ||
packages: | ||
a: 1.0.0 | ||
b: 2.0.0 | ||
explanation: The latest valid version of `b` should be installed. `b==3.0.0` is | ||
not valid because it requires `c` which does not exist. | ||
root: | ||
requires: | ||
- a | ||
packages: | ||
a: | ||
versions: | ||
1.0.0: | ||
requires: | ||
- b>1.0.0 | ||
b: | ||
versions: | ||
1.0.0: {} | ||
2.0.0: {} | ||
3.0.0: | ||
requires: | ||
- c |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.