[STORY] Override of field type in task interface auto-port script #221
Labels
analysis-design
Complex analysis workflow epic
mid-level
Requires moderate framework/domain-specific knowledge
pipelines
story
a unit of work
Metadata
Epic: #17
Feature: #217
Feature Release:
Required knowledge: mid-level
Description
As a developer porting Nipype to Pydra, I want to be able to override the "type" of fields copied from the Nipype interface, so that we can handle the case where the type was specified too loosely in Nipype for the requirements of the ported field (i.e. if it has an "output_file_template" attribute)
Acceptance Criteria
The text was updated successfully, but these errors were encountered: