Gathering detailed insights and metrics for graphql-relay
Gathering detailed insights and metrics for graphql-relay
Gathering detailed insights and metrics for graphql-relay
Gathering detailed insights and metrics for graphql-relay
nestjs-graphql-relay
@nestjs/graphql + graphql-relay + typeorm
graphql-sequelize
GraphQL & Relay for MySQL & Postgres via Sequelize
@prodigyems/graphql-sequelize
GraphQL & Relay for MySQL & Postgres via Sequelize
date-graphql-sequelize
GraphQL & Relay for MySQL & Postgres via Sequelize
A library to help construct a graphql-js server supporting react-relay.
npm install graphql-relay
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
1,543 Stars
335 Commits
182 Forks
71 Watching
6 Branches
71 Contributors
Updated on 14 Nov 2024
TypeScript (85.16%)
JavaScript (14.84%)
Cumulative downloads
Total Downloads
Last day
-3.4%
32,351
Compared to previous day
Last week
-7.2%
161,428
Compared to previous week
Last month
11%
675,760
Compared to previous month
Last year
14.7%
8,207,448
Compared to previous year
1
This is a library to allow the easy creation of Relay-compliant servers using the GraphQL.js reference implementation of a GraphQL server.
A basic understanding of GraphQL and of the GraphQL.js implementation is needed to provide context for this library.
An overview of GraphQL in general is available in the README for the Specification for GraphQL.
This library is designed to work with the GraphQL.js reference implementation of a GraphQL server.
An overview of the functionality that a Relay-compliant GraphQL server should provide is in the GraphQL Relay Specification on the Relay website. That overview describes a simple set of examples that exist as tests in this repository. A good way to get started with this repository is to walk through that documentation and the corresponding tests in this library together.
Install Relay Library for GraphQL.js
1npm install graphql graphql-relay
When building a schema for GraphQL.js, the provided library functions can be used to simplify the creation of Relay patterns.
Helper functions are provided for both building the GraphQL types for connections and for implementing the resolve
method for fields returning those types.
connectionArgs
returns the arguments that fields should provide when they return a connection type that supports bidirectional pagination.forwardConnectionArgs
returns the arguments that fields should provide when they return a connection type that only supports forward pagination.backwardConnectionArgs
returns the arguments that fields should provide when they return a connection type that only supports backward pagination.connectionDefinitions
returns a connectionType
and its associated edgeType
, given a node type.connectionFromArray
is a helper method that takes an array and the arguments from connectionArgs
, does pagination and filtering, and returns an object in the shape expected by a connectionType
's resolve
function.connectionFromPromisedArray
is similar to connectionFromArray
, but it takes a promise that resolves to an array, and returns a promise that resolves to the expected shape by connectionType
.cursorForObjectInConnection
is a helper method that takes an array and a member object, and returns a cursor for use in the mutation payload.offsetToCursor
takes the index of a member object in an array and returns an opaque cursor for use in the mutation payload.cursorToOffset
takes an opaque cursor (created with offsetToCursor
) and returns the corresponding array index.An example usage of these methods from the test schema:
1var { connectionType: ShipConnection } = connectionDefinitions({ 2 nodeType: shipType, 3}); 4var factionType = new GraphQLObjectType({ 5 name: 'Faction', 6 fields: () => ({ 7 ships: { 8 type: ShipConnection, 9 args: connectionArgs, 10 resolve: (faction, args) => 11 connectionFromArray( 12 faction.ships.map((id) => data.Ship[id]), 13 args, 14 ), 15 }, 16 }), 17});
This shows adding a ships
field to the Faction
object that is a connection. It uses connectionDefinitions({nodeType: shipType})
to create the connection type, adds connectionArgs
as arguments on this function, and then implements the resolve function by passing the array of ships and the arguments to connectionFromArray
.
Helper functions are provided for both building the GraphQL types for nodes and for implementing global IDs around local IDs.
nodeDefinitions
returns the Node
interface that objects can implement, and returns the node
root field to include on the query type. To implement this, it takes a function to resolve an ID to an object, and to determine the type of a given object.toGlobalId
takes a type name and an ID specific to that type name, and returns a "global ID" that is unique among all types.fromGlobalId
takes the "global ID" created by toGlobalID
, and returns the type name and ID used to create it.globalIdField
creates the configuration for an id
field on a node.pluralIdentifyingRootField
creates a field that accepts a list of non-ID identifiers (like a username) and maps them to their corresponding objects.An example usage of these methods from the test schema:
1var { nodeInterface, nodeField } = nodeDefinitions( 2 (globalId) => { 3 var { type, id } = fromGlobalId(globalId); 4 return data[type][id]; 5 }, 6 (obj) => { 7 return obj.ships ? factionType : shipType; 8 }, 9); 10 11var factionType = new GraphQLObjectType({ 12 name: 'Faction', 13 fields: () => ({ 14 id: globalIdField(), 15 }), 16 interfaces: [nodeInterface], 17}); 18 19var queryType = new GraphQLObjectType({ 20 name: 'Query', 21 fields: () => ({ 22 node: nodeField, 23 }), 24});
This uses nodeDefinitions
to construct the Node
interface and the node
field; it uses fromGlobalId
to resolve the IDs passed in the implementation of the function mapping ID to object. It then uses the globalIdField
method to create the id
field on Faction
, which also ensures implements the nodeInterface
. Finally, it adds the node
field to the query type, using the nodeField
returned by nodeDefinitions
.
A helper function is provided for building mutations with single inputs and client mutation IDs.
mutationWithClientMutationId
takes a name, input fields, output fields, and a mutation method to map from the input fields to the output fields, performing the mutation along the way. It then creates and returns a field configuration that can be used as a top-level field on the mutation type.An example usage of these methods from the test schema:
1var shipMutation = mutationWithClientMutationId({ 2 name: 'IntroduceShip', 3 inputFields: { 4 shipName: { 5 type: new GraphQLNonNull(GraphQLString), 6 }, 7 factionId: { 8 type: new GraphQLNonNull(GraphQLID), 9 }, 10 }, 11 outputFields: { 12 ship: { 13 type: shipType, 14 resolve: (payload) => data['Ship'][payload.shipId], 15 }, 16 faction: { 17 type: factionType, 18 resolve: (payload) => data['Faction'][payload.factionId], 19 }, 20 }, 21 mutateAndGetPayload: ({ shipName, factionId }) => { 22 var newShip = { 23 id: getNewShipId(), 24 name: shipName, 25 }; 26 data.Ship[newShip.id] = newShip; 27 data.Faction[factionId].ships.push(newShip.id); 28 return { 29 shipId: newShip.id, 30 factionId: factionId, 31 }; 32 }, 33}); 34 35var mutationType = new GraphQLObjectType({ 36 name: 'Mutation', 37 fields: () => ({ 38 introduceShip: shipMutation, 39 }), 40});
This code creates a mutation named IntroduceShip
, which takes a faction ID and a ship name as input. It outputs the Faction
and the Ship
in question. mutateAndGetPayload
then gets an object with a property for each input field, performs the mutation by constructing the new ship, then returns an object that will be resolved by the output fields.
Our mutation type then creates the introduceShip
field using the return value of mutationWithClientMutationId
.
After cloning this repo, ensure dependencies are installed by running:
1npm install
This library is written in ES6 and uses Babel for ES5 transpilation and TypeScript for type safety. Widely consumable JavaScript can be produced by running:
1npm run build
Once npm run build
has run, you may import
or require()
directly from node.
After developing, the full test suite can be evaluated by running:
1npm test
We actively welcome pull requests. Learn how to contribute.
This repository is managed by EasyCLA. Project participants must sign the free (GraphQL Specification Membership agreement before making a contribution. You only need to do this one time, and it can be signed by individual contributors or their employers.
To initiate the signature process please open a PR against this repo. The EasyCLA bot will block the merge if we still need a membership agreement from you.
You can find detailed information here. If you have issues, please email operations@graphql.org.
If your company benefits from GraphQL and you would like to provide essential financial support for the systems and people that power our community, please also consider membership in the GraphQL Foundation.
Changes are tracked as GitHub releases.
graphql-relay-js is MIT licensed.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
2 existing vulnerabilities detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 4
Details
Reason
Found 8/27 approved changesets -- score normalized to 2
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More