[modern] Range_Delete configs requires two levels on pathToConnection
- Dominant language
- Rust
- Stars
- 19k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
Assessment
This issue has not been assessed yet.