common-workflow-language / common-workflow-language/cwl-utils
docker_extract.py is not handling relative directories very well.
- Dominant language
- Python
- Stars
- 43
- Forks
- 28
- Avg merge
- 4h 7m
- Merged PRs (30d)
- 4
Description
Hi - I'm curious how up to date and stable this package is. It seems like parsing a CWL 1.2 workflow works in some ways but not others. I can parse a workflow when its stored unpacked, but can't parse a workflow when its packed. I can use load_document_by_uri but can't use cwl_utils.parser.cwl_v1_2.load_document
Depending on how a document is stored/loaded, I'm running into different issues traversing the workflow steps. I'm trying to use the docker_extract.py script as an example. I'm wondering if there is a right way of using this package and/or a wrong way.
Contributor guide
Research direction
Start with docker_extract.py and compare how packed and unpacked CWL 1.2 workflows are loaded through load_document_by_uri and cwl_utils.parser.cwl_v1_2.load_document. Trace how relative directories affect workflow-step traversal. Done means the supported loading approach is clear and relative directories work consistently for the reported workflow forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100