Merge lp://qastaging/~mterry/snapcraft/yaml-info into lp://qastaging/~snappy-dev/snapcraft/abandoned-go-trunk
Status: | Merged |
---|---|
Approved by: | Michael Terry |
Approved revision: | 7 |
Merged at revision: | 4 |
Proposed branch: | lp://qastaging/~mterry/snapcraft/yaml-info |
Merge into: | lp://qastaging/~snappy-dev/snapcraft/abandoned-go-trunk |
Diff against target: |
497 lines (+399/-10) 10 files modified
cmd/snapcraft/cmd_scratch.go (+30/-0) cmd/snapcraft/cmd_scratch_info.go (+66/-0) cmd/snapcraft/cmd_scratch_info_test.go (+68/-0) cmd/snapcraft/parse.go (+23/-4) cmd/snapcraft/parse_test.go (+21/-5) config/yaml.go (+70/-0) config/yaml_test.go (+97/-0) dependencies.tsv (+1/-0) docs/yaml.md (+21/-1) gen-coverage.sh (+2/-0) |
To merge this branch: | bzr merge lp://qastaging/~mterry/snapcraft/yaml-info |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Michael Vogt (community) | Approve | ||
Ted Gould | Pending | ||
Review via email:
|
Commit message
Add basic yaml parsing and simple 'xscratch info' command.
This is just a code drop for some stuff I think we'll need in SOME form, even if it changes slightly down the road.
There are two main additions here. One is a config module that handles parsing our snappy.yaml format. Just basic stuff so far.
And the other is a new command to actually exercise that code, by dumping out the scratch build environment's configuration (which we don't have any code to actually manage yet, but one can fake it).
I've followed the example of our existing specification and used "x-" liberally to make sure everyone understands things are in flux. Even for the 'scratch' command, where I've used 'xscratch' instead.
And I've kept our unit test coverage at 100%. Woo!
Description of the change
Add basic yaml parsing and simple 'xscratch info' command.
This is just a code drop for some stuff I think we'll need in SOME form, even if it changes slightly down the road.
There are two main additions here. One is a config module that handles parsing our snappy.yaml format. Just basic stuff so far.
And the other is a new command to actually exercise that code, by dumping out the scratch build environment's configuration (which we don't have any code to actually manage yet, but one can fake it).
I've followed the example of our existing specification and used "x-" liberally to make sure everyone understands things are in flux. Even for the 'scratch' command, where I've used 'xscratch' instead.
And I've kept our unit test coverage at 100%. Woo!
Nice work! I added some inline comments but its mostly nitpicking, feel free to ignore.