Skip to content
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

[modern] Range_Delete configs requires two levels on pathToConnection #1996

Open
IkerArb opened this issue Jul 25, 2017 · 2 comments
Open

[modern] Range_Delete configs requires two levels on pathToConnection #1996

IkerArb opened this issue Jul 25, 2017 · 2 comments

Comments

@IkerArb
Copy link

IkerArb commented Jul 25, 2017

I have been using the ConnectionHandler and writing manually my updater and optimistic updater and getting the connection in the next way:

const viewerProxy = store.get(viewerId);
const connection = ConnectionHandler.getConnection(
    viewerProxy,
    connectionKey,
);

But I noticed on the documentation that you have Range_Delete: https://facebook.github.io/relay/docs/mutations.html#range-delete

My question is why do you do this validation that it should have two levels up until the connection? https://github.com/facebook/relay/blob/master/packages/relay-runtime/mutations/setRelayModernMutationConfigs.js#L273

I want to know if I have a wrong design in my payload or store design.

@khalilchris
Copy link

hello

@stale
Copy link

stale bot commented Dec 25, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants