FIX remove legacyForwarding true in test that does not need it #4604
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.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does a .test simplification, removing legacyForwarding: true (a deprecated feature) in test that don't need it. They are probably old test developed in the times when NGSIv2 forwarding was not fully working.
After this PR the only tree .test that use legacyForwarding: true are he following ones:
In addition, note that none of these remaining test is actually implementing a NGSIv1 forwarding case. A .test for that is going to be added in PR #4603, to test the new parser developed for that.