to use forEach instead of map function in with-apollo example

[ArianHamdi]

Verify canary release

• I verified that the issue exists in Next.js canary release

Provide environment information

Not relevant

Which example does this report relate to?

with-apollo

Describe the Bug

There is no bug but it is better to use forEach function instead of map function because we don't care about the value that is retunded by map function.

const errorLink = onError(({ graphQLErrors, networkError }) => {
  if (graphQLErrors)
    graphQLErrors.map(({ message, locations, path }) =>
      console.log(
        `[GraphQL error]: Message: ${message}, Location: ${locations}, Path: ${path}`
      )
    )
  if (networkError) console.log(`[Network error]: ${networkError}`)
})

Expected Behavior

const errorLink = onError(({ graphQLErrors, networkError }) => {
  if (graphQLErrors)
    graphQLErrors.forEach(({ message, locations, path }) =>
      console.log(
        `[GraphQL error]: Message: ${message}, Location: ${locations}, Path: ${path}`
      )
    )
  if (networkError) console.log(`[Network error]: ${networkError}`)
})

To Reproduce

clone with-apollo example and look at lib/apolloClient.js

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.