common-workflow-language / common-workflow-language/cwl-v1.3

language cleanups

Open
#33 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Common Workflow Language
Stars
6
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Goal: move essential features from "Requirement" to regular features, and make optional the requirements that only exist to indicate a certain feature is used in the document.

Command line tool

InitialWorkDirRequirement

Becomes "initialWorkDir" optional field of CommandLineTool, with the same schema and semantics as InitialWorkDirRequirement "listing" field.

EnvVarRequirement

Becomes "envDef" optional field of CommandLineTool, with same schema and sematics as EnvVarRequirement "envDef".

NetworkAccess

Becomes "networkAccess" optional field of CommandLineTool, with same schema and sematics as NetworkAccess "networkAccess".

ShellCommandRequirement

See #44

Workflows

SubworkflowFeatureRequirement

This becomes optional. This feature is allowed by default.

ScatterFeatureRequirement

This becomes optional. This feature is allowed by default.

MultipleInputFeatureRequirement

This becomes optional. This feature is allowed by default.

StepInputExpressionRequirement

This becomes optional. This feature is allowed by default.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the CommandLineTool and workflow requirement sections in this issue, then follow the reference to #44 for ShellCommandRequirement. Map each listed requirement to its proposed optional field or default behavior, and confirm the resulting schema and semantics before considering the cleanup complete.

Written by the indexing model from the issue text.

Assessment

Domain
data-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.