Update authorization and pagination docs

[mandiwise]

Description

This PR contains updated authorization and pagination content for the Learn docs. Key changes include:

• Intro and recap formats are standardized with other updated pages
• Example resolver format has been standardized with the rest of the docs
• The postRepository code example has been expanded for clarity
• Nod to auth directives (given that this is a common pattern)
• Schema examples for connection and edge types are include on the pagination page
• Light editing throughout each page

@benjie @jorydotcom

[vercel]

@mandiwise is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel.

A member of the Team first needs to authorize it.

[benjie]

Some really good changes here, but I'm not sure about "Using type system directives" being included?

[benjie]

Following on from https://github.com/graphql/graphql.github.io/pull/1814/files#r1852923240

Instead of trying to fit the auth directive approach into the "business logic layer" narrative, let's explicitly call it out as an alternative - something that people do but is not the recommended way:

Suggested change

	In the example above, we saw how authorization logic can be delegated to the business logic layer through a function that is called in a field resolver.
	In the example above, we saw how authorization logic can be delegated to the business logic layer through a function that is called in a field resolver. In general it is recommended to perform all authorization logic in the business logic layer, however if you decide to implement authorization in the GraphQL layer instead then one approach is to use [type system dire...

(merge with next paragraph)

The remainder of the text in this section would also need light editorial to reflect this.

What do you think?

[mandiwise]

Sounds good, addressed in 587906a.

[benjie]

We're back to 136 files changed @mandiwise; I think something went wrong with your merge/rebase

[mandiwise]

@benjie I tried to sync my fork's branch with source before fixing the commit history issue and something went haywire in Github and it auto-closed this PR. I can't reopen the PR, so let me know if you can do this from your end or if you'd like me to create a new branch. I should have everything we've done so far locally.

Update: I dug into this further was able to figure out what needed to be done for the PR to be re-openable. I was also able to remove the duplicated file changes from the source branch again.

[benjie]

This looks good to go to me! 🙌

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
graphql-github-io	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 28, 2024 4:23pm