Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the path to GraphQL Server Specification for Relay #1432

Conversation

rapsealk
Copy link
Contributor

Hello graphene-django!

This PR updates the location of GraphQL Relay Specification with the latest valid URL.

@rapsealk rapsealk changed the title docs: Update location of GraphQL Relay Specification Update the location of GraphQL Relay Specification Jul 16, 2023
@rapsealk rapsealk changed the title Update the location of GraphQL Relay Specification Update the path to GraphQL Relay Specification Jul 16, 2023
@rapsealk rapsealk changed the title Update the path to GraphQL Relay Specification Update the path to GraphQL Relay Specification for Relay Jul 16, 2023
@rapsealk rapsealk changed the title Update the path to GraphQL Relay Specification for Relay Update the path to GraphQL Server Specification for Relay Jul 16, 2023
Copy link
Collaborator

@sjdemartini sjdemartini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@firaskafri firaskafri merged commit 3f061a0 into graphql-python:main Jul 18, 2023
13 checks passed
@rapsealk rapsealk deleted the docs/update-graphql-relay-spec-location branch July 19, 2023 00:02
superlevure pushed a commit to loft-orbital/graphene-django that referenced this pull request Jul 19, 2023
@rapsealk rapsealk restored the docs/update-graphql-relay-spec-location branch August 23, 2023 14:52
@rapsealk rapsealk deleted the docs/update-graphql-relay-spec-location branch August 23, 2023 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants