This adds the force_dataype key value pair into the step dict on the backend, which means that subworkflows outputs and tools that have a change datatype PJA will display the correct output datatype.
The client now also sets force_datatype when changing the PJA and updates the node's output label to indicate the new output datatype.
This has some caveats here: We don't store the original
datatype, so if we want to switch back to whatever the
tool produces you have to know the datatype.
Probably need an additional attribute on the output
terminal that si the actual tool extension.
Removed the karma test that checks whether a PJA to an unrelated
output doesn't affect the current output.
This is now determined on the backend (allows PJAs to have an effect
in the workflow editor), so I removed this test.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.