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
[ ] 1. Types of ported fields can be manually specified before the script is run
[ ] 2. The solution is in the style of other manual overrides
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