1.2 spec conformance: allow None values for call inputs where the input is non-optional in type but has a default value

[peterhuene]

According to the spec, inputs with a default value should accept None regardless of the type of the input being optional; the intention is to signify that the call should always use the default value for the input (i.e. cannot be overridden by a nested input).

version 1.2

task foo {
    input {
        Int i = 1
    }

    command <<<
        echo ~{i}
    >>>
}

workflow bar {
    call foo {
        i = None
    }
}

The task should print 1.

Instead, we error from static analysis:

error: type mismatch: expected type `Int`, but found type `None`
   ┌─ foo.wdl:15:13
   │
15 │         i = None
   │         -   ^^^^ this is type `None`
   │         │    
   │         this expects type `Int`

error: aborting due to previous diagnostic

[HenryNg101]

Hey, I would like to work on this issue :) may I give it a go @peterhuene ?

[peterhuene]

Hi @HenryNg101. Feel free to take a stab at it. Please let me know if you into any issues, thanks!

[Nitish-bot]

Hey! This has been inactive for 2 weeks now so I have started to work on this, could I get assigned?