Mention the ability to disable output connections #433
Conversation
|
Delegation to |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #433 +/- ##
=======================================
Coverage 80.22% 80.22%
=======================================
Files 96 96
Lines 10975 10975
Branches 2099 2099
=======================================
Hits 8805 8805
Misses 1823 1823
Partials 347 347 ☔ View full report in Codecov by Sentry. |
| Note that the same mechanism works for output connections: | ||
| an output from a `PipelineTask` can be made optional (under config control) | ||
| or a config switch can even be used to choose between different ways of | ||
| providing output. |
There was a problem hiding this comment.
Might be worth clarifying that this is different from making an input optional at runtime by setting minimum=0 in the Input connection declaration. In the configuration case, the connection is treated as if it never existed by QG generation and execution code, while minimum=0 allows a quantum to be generated and run even no dataset for that input are found. (There is no minimum for Output connections because they are always considered runtime-optional.)
There was a problem hiding this comment.
Let me know if you think I've captured it now.
gpdf
force-pushed
the
u/gpdf/optional-outputs-1
branch
from
a599c83
to
1029755
Compare
gpdf
force-pushed
the
u/gpdf/optional-outputs-1
branch
from
1029755
to
31565d2
Compare
|
Squashed commits in preparation for merge |
Checklist
doc/changesReviewer: please advise on whether "necessary" or "recommended" is more correct in:
"It is now no longer ( necessary / recommended ) to delegate to
superin either case,"There was clearly a word missing in any event.