Skip to content

Commit

Permalink
Change all links from graphql-rules.com to github (#2459)
Browse files Browse the repository at this point in the history
* Change all links from graphql-rules.com to github as the domain graphql-rules.com is dead

* use README.md as root instead of directory index
  • Loading branch information
k0ka authored Oct 31, 2023
1 parent 50b150f commit 889c7bc
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
4 changes: 2 additions & 2 deletions docs/6/the-basics/best-practices.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Best Practices

When starting out with developing a GraphQL API, it is a good idea to look at existing best practices.
We recommend you use [GraphQL Rules](https://graphql-rules.com) and the following tips as a starting point
We recommend you use [GraphQL Rules](https://github.com/graphql-rules/graphql-rules/blob/master/docs/rules/README.md) and the following tips as a starting point
to develop a set of guidelines that works for you.

## In the mutation response, return a field of type Query

If you decide to [return the `Query` object in every mutation payload](https://graphql-rules.com/rules/mutation-payload-query),
If you decide to [return the `Query` object in every mutation payload](https://github.com/graphql-rules/graphql-rules/blob/master/docs/rules/06-mutations/mutation-payload-query.md),
Lighthouse makes it very easy.

```graphql
Expand Down
4 changes: 2 additions & 2 deletions docs/master/the-basics/best-practices.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Best Practices

When starting out with developing a GraphQL API, it is a good idea to look at existing best practices.
We recommend you use [GraphQL Rules](https://graphql-rules.com) and the following tips as a starting point
We recommend you use [GraphQL Rules](https://github.com/graphql-rules/graphql-rules/blob/master/docs/rules/README.md) and the following tips as a starting point
to develop a set of guidelines that works for you.

## In the mutation response, return a field of type Query

If you decide to [return the `Query` object in every mutation payload](https://graphql-rules.com/rules/mutation-payload-query),
If you decide to [return the `Query` object in every mutation payload](https://github.com/graphql-rules/graphql-rules/blob/master/docs/rules/06-mutations/mutation-payload-query.md),
Lighthouse makes it very easy.

```graphql
Expand Down
2 changes: 1 addition & 1 deletion tests/Integration/Schema/ResolverProviderTest.php
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ public function testNonRootFields(): void
]);
}

/** @see https://graphql-rules.com/rules/mutation-payload-query */
/** @see https://github.com/graphql-rules/graphql-rules/blob/master/docs/rules/06-mutations/mutation-payload-query.md */
public function testRootQueryMutationPayload(): void
{
$fooResult = 1;
Expand Down

0 comments on commit 889c7bc

Please sign in to comment.