Fix: values order with non-GET requests #2749
Merged
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.
Description
Former implementation of
overrideFormData
was overriding all values for a given key, one key after the other, thus breaking the initial order of values.This situation wasn't caught by existing tests (see 01b292a), as the tested case was a
GET
request, for which we don't run the values override with the closest form's values.This PR fixes #2703 by overriding values in order using
forEach
on theFormData
, ensuring to preserve the initial orderCorresponding issue: #2703
Testing
Added a test case for a
POST
request as wellChecklist
master
for website changes,dev
forsource changes)
approved via an issue
npm run test
) and verified that it succeeded