Duke-GCB / Duke-GCB/bespin-cli

Usability improvements for including files

Open
#21 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

When describing a file, bespin-cli requires a CWL File object structure. For example, an array of two files at `['/path/to/file1','/path/to/file2']` requires the following structure:

```
[
{
"class": "File",
"path": "/path/to/file1"
},
{
"class": "File",
"path": "/path/to/file2"
}
]
```

User feedback on this requirement was that

1. The added boilerplate (class, path,) make the important pieces (file name) to identify when comparing lines or files
2. Authoring/editing such files by hand is error prone
3. Copying/pasting the structure is expected and may lead to hard-to-spot errors.

Related to #19

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.