[GraphQL]: Add Relay support

[buffalojoec]

Motivation

The GraphQL package can be much easier to integrate into web applications if it adheres to the Relay specification and can be used by apps powered by Relay.

One of the biggest schema changes required to be Relay-compliant will be the use of an ID field.

[tibi77]

hey @buffalojoec!
I'm interested in picking this one up. From my understanding the gameplan shall be the following:

1. add id to all the schemas from packages/rpc-graphql/src/schema
2. add tests specific for Relay inside the schemas tests

Is there any change needed inside the resolvers or loaders?

From the specification in the provided link i can see that ID is a required field, shall that be the case for this PR as well; or shall it be optional?

Thanks

[buffalojoec]

Hi @tibi77 thanks for reaching out!

I think you've generalized it pretty well here, although we don't know how much of an effort it will be to be completely compliant with the Relay spec until we've started to uncover a few stones in the schema and their docs.

For example, we might have to investigate pagination and cursor connections, but I think the ID and the tests are a good place to start.

It's worth noting that we actually have suitable identifiers for each schema object.

• Account: Address
• Block: Slot
• Transaction: Signature

I think we just need to hack around and see how practical it might be to either:

1. Replace those fields (address, slot, signature) with the field name id.
2. Simply duplicate them under the id field name.

Both are pretty gross for their own reasons, but it won't become clear which is the better move until we've messed around with it up close.

[tibi77]

@buffalojoec opened a draft just for the transactions; curious if i m doing it correctly
also, when i run pnpm run test inside the root, i can not see the rpc-graphql being run. And if i go into the folder packages/rpc-graphql and run npm run test:unit:node i get

i think I m missing something about running those tests

[buffalojoec]

@tibi77 Try making sure you don't have a test validator running, and then from the workspace root run scripts/setup-test-validator.sh. That will download a Solana binary to the workspace and allow the tests to spin up a local validator to run the unit tests. Don't worry about starting it. The test command will do start and stop.

[tibi77]

ohhh nice; thanks for that
they seem to work 💪