Multiple package dependencies aka quilt.yml
Description
Similar to requirements.txt, users need a way to specify that a project depends on one or more package instances: quilt3 install @quilt.yml see here
TODO
- [x] Unit Tests
- [x] Documentation
Codecov Report
Merging #1768 into master will decrease coverage by
4.11%. The diff coverage is96.46%.
@@ Coverage Diff @@
## master #1768 +/- ##
==========================================
- Coverage 89.49% 85.37% -4.12%
==========================================
Files 62 60 -2
Lines 7233 7181 -52
==========================================
- Hits 6473 6131 -342
- Misses 760 1050 +290
| Flag | Coverage Δ | |
|---|---|---|
| #api-python | 88.06% <96.46%> (+0.19%) |
:arrow_up: |
| #lambda | 80.25% <ø> (-12.07%) |
:arrow_down: |
Flags with carried forward coverage won't be shown. Click here to find out more.
| Impacted Files | Coverage Δ | |
|---|---|---|
| api/python/quilt3/main.py | 58.00% <93.75%> (+2.14%) |
:arrow_up: |
| api/python/quilt3/util.py | 84.02% <94.82%> (+2.17%) |
:arrow_up: |
| api/python/tests/test_cli.py | 100.00% <100.00%> (ø) |
|
| api/python/tests/test_util.py | 100.00% <100.00%> (ø) |
|
| lambdas/s3select/index.py | 0.00% <0.00%> (-100.00%) |
:arrow_down: |
| lambdas/s3select/tests/test_s3select.py | 0.00% <0.00%> (-100.00%) |
:arrow_down: |
| lambdas/pkgselect/test/test_pkgselect.py | 0.00% <0.00%> (-100.00%) |
:arrow_down: |
| lambdas/pkgselect/index.py | 0.00% <0.00%> (-84.06%) |
:arrow_down: |
| lambdas/shared/t4_lambda_shared/utils.py | 95.89% <0.00%> (-2.74%) |
:arrow_down: |
| lambdas/access_counts/index.py | ||
| ... and 1 more |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update a5945a1...d0a64aa. Read the comment docs.
@cosmic-byte, could you rebase this please? (don't forget to isort before push)
Need a full docs section on file syntax with examples.
@akarve I updated the cli docs with install example and syntax.
I guess this is not exactly what you requested, so can you suggest a better way of documenting CLI?
Closing in favor of forthcoming data.yaml