-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(flow): flow-operations tries to spread inexact objects #8000 #15
feat(flow): flow-operations tries to spread inexact objects #8000 #15
Conversation
Hi @Athelian, Thank you for your contribution! ⚡ Could you check the following:
Thank you! |
Hi @charlypoly. I think And please lmk if you would prefer I rebase this PR instead of merge. Thank you. |
Hey @Athelian can you please rebase this PR and hopefully that should make all tests pass then we can merge |
Before this change, only inner fragments are made exact
e68477d
to
6adb328
Compare
🦋 Changeset detectedLatest commit: f522b78 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Done! |
hey @Athelian can you please add a test for this change and also run |
Hi @saihaj I added the changeset. As for a new test, I am not sure if it is necessary: All pre-existing tests needed updating, and all differences between true/false can covered by |
CI is still failing @Athelian |
Failing CI looks working to me now if replicate in local. Sorry for trouble. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you for fixing!
🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
Description
Flow-operations tries to spread exact/inexact objects into the same merged object which leads to flow errrors.
I have already been running with this change in a custom plugin for quite some time.
Related issue #8000
Type of change
Please delete options that are not relevant.
Screenshots/Sandbox (if appropriate/relevant):
Flow Try demonstrating the issue
How Has This Been Tested?
Pre-existing test demonstrates difference between
useFlowExactObjects=false/true
Test Environment:
@graphql-codegen/flow-operations
version: ^2.2.13Checklist:
Further comments
Forked from legacy repo