graphile / graphile/federation

Add @key as primary key fields instead of nodeId

Open
#1 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
41
Forks
11
PR merge metrics
No merged PRs in 30d

Description

When using Graphile federated with another service, it seems to make more sense for the key to be on the primary keys of the resource instead of the `nodeId`. This is because any other resource would be likely to have access to the resource by its primary keys.

This can be worked around by adding `@requires(fields: {primary keys})` to each other field and fetching by the keys in `__resolveReference` but this seemed like a bad solution.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.