add_fields_to always raises FieldExistsWarning on failure
add_fields_to accepts a batch of fields in form of a dict
add_fields_to can take a Rule as argument now, needed to raise proper FieldExistsWarning; is optional because of use of add_fields_to outside from processors, e.g. InputConnectors
Refactor add_fields_to function for clarity and consistency.
Update unit tests to reflect new exception handling logic.
Update code and tests to utilize new add_fields_to (especially processors)
ToDo:
[x] Add tests for adding multiple fields with add_fields_to method
[x] rethink usage of _write_target_field in abc/processor.py
add_field_totoadd_fields_toadd_fields_toalways raisesFieldExistsWarningon failureadd_fields_toaccepts a batch of fields in form of a dictadd_fields_tocan take a Rule as argument now, needed to raise properFieldExistsWarning; is optional because of use ofadd_fields_tooutside from processors, e.g. InputConnectorsadd_fields_tofunction for clarity and consistency.add_fields_to(especially processors)ToDo:
add_fields_tomethod_write_target_fieldinabc/processor.py