Relay querying by id

[ro-savage]

Hasura's where clauses in relay only accept the database id, and not the relay id.

This causes a bunch of issues around querying.

If I want to get a project by the id. I must use the node interface instead of the project_connection interface. This means I lose a bunch of auto-complete that's built into different IDEs because they no longer know the data structure that is being returned.

If I want to find all assignments by the project id, I can not query assignments_connection(where: {project_id: {_eq: }}) because it only accepts the database id and not the relay id.

When you are using relay on the frontend, you should only have to worry about the id relay uses. Not try to decipher the database ids.

[aakside]

Is there a work-around for this that doesn't require the client to deal with any database IDs?

If not, can someone tell me (or point me to relevant code) how relay IDs are transformed into types/IDs (and vice-versa)?

[aakside]

Never mind, I see that the relay IDs are base64-encoded arrays. For anyone curious, just base64-decode a few IDs and you'll see how they are structured.

[Albert-Gao]

How could you guys add the record to Relay Store after mutation, I stuck at retrieving the edge from the server response.

mutation CreateTaskMutation($input: task_insert_input!) {
        insert_task_one(object: $input) {
          id
          title
          due_date
          due_time
          description
        }
      }

I got the server response from store.getRootField

const serverResponse = store.getRootField('insert_task_one')

Then how to retrieve the edge? There is no nesting after insert_task_one in that GraphQL query.

const serverEdge = payload.getLinkedRecord(WHAT_SHOULD_I_PUT_HERE);

How to get the edge from the response so I can write to the Relay Store later with ConnectionHandler.insertEdgeAfter()?

Thanks :)

[jarofghosts]

Both of these issues are important to me as well. I've managed to work around the former by doing ID -> PK decoding on the client, but it doesn't feel great. However, the mutation responses not including the edge makes writing updater configs impossible (as far as I can tell).

[Albert-Gao]

Not impossible, you just have to create the edge by yourself, I haven't done that because now I need to know how to construct a relay style id (the one they use to store item in RelayStore), and TBH, I use Relay experimental and I have no idea.

The team is working on that, so I will wait until the next release, my project is current in dev, so the optimistic update can be leaved later

[jarofghosts]

I'm not sure how that would work, actually. I'm talking specifically about using the updater configs method for updates.

[crieggalder]

+1 - this is a problem for our team too. I suggest going with Postgraphile's strategy of naming the Relay id "nodeId" to avoid conflicts with "id" fields in tables: https://www.graphile.org/postgraphile/node-id/