Fix/mock payload generator plural double nest - #5387
Conversation
|
Hi @vchernovatl! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
6bdfb89 to
3e143d3
Compare
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Summary
MockPayloadGeneratorproduced a double-nested list ([[item]]instead of[item]) when the same plural linked field is selected twice at one path —once unconditionally and once in a sibling
@include/@skipcondition orabstract inline fragment. The normalizer then couldn't read the leaf fields
(
Payload did not contain a value for field ...).Cause: in
_mockLink'sgenerateDataForField, the whole prior array waspassed as each element's previous value, so it got wrapped again. Fix: index
the prior array by
indexfor plural fields (asfieldPathalready is).Fixes #5258.
Test plan
Added regression tests for the
@includeand concrete+abstract-fragment shapes(via
testGeneratedData, so the normalizer runs underdisallowWarnings()).yarn jest— 243 suites / 3739 tests pass (fail without the fix)flow,prettier --check,eslint— clean