Skip to content

Do not evaluate expressions with self if input object is null #630

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from

Conversation

anton-khodak
Copy link
Member

fixes #621

@anton-khodak anton-khodak force-pushed the fix/js-expr-for-null-inputs branch 2 times, most recently from f00507f to daaaa53 Compare January 28, 2018 13:38
@mr-c
Copy link
Member

mr-c commented Jan 28, 2018

@anton-khodak Thanks! Can you make a conformance test for this in the main CWL repo so we can confirm that this is the correct behavior? Once that is approved then we can merge this

@mr-c
Copy link
Member

mr-c commented Jan 29, 2018

@mr-c
Copy link
Member

mr-c commented Jan 29, 2018

@anton-khodak Looks like someone needs to add location fields for tests with Directory outputs.

@mr-c
Copy link
Member

mr-c commented Jan 29, 2018

@anton-khodak or rather, if no location field is expected then don't fail on one being provided

@mr-c
Copy link
Member

mr-c commented Jan 30, 2018

Jenkins, test this please

1 similar comment
@mr-c
Copy link
Member

mr-c commented Jan 30, 2018

Jenkins, test this please

@mr-c
Copy link
Member

mr-c commented Jan 30, 2018

Thanks! I'm combing this with #628 into a single PR: #632

@mr-c mr-c closed this Jan 30, 2018
@mr-c mr-c deleted the fix/js-expr-for-null-inputs branch January 30, 2018 11:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Staging an optional file error
2 participants