getting started , meetup graph ql

because-meetup-breaks.md

Meetup api shut down rest

and the graph ql docs are not good

https://www.meetup.com/api/guide/#graphQl-guide

The out of the box example does not work.
However, this version is works:

query='query { self { id name } }'
YOUR_TOKEN='put-a-token'
curl -X POST https://api.meetup.com/gql \
  -H "Authorization: Bearer $YOUR_TOKEN" \
  -H 'Content-Type: application/json' \
  -d @- <<EOF
    {"query": "$query"}
EOF

expected output:
{"data":{"self":{"id":"1234567","name":"Example User"}}}

https://www.meetup.com/api/oauth/list/

query upcoming events:

query='query { self { id name upcomingEvents { pageInfo { startCursor } count edges { node { title } } } } }'

it will look something like this in javascript
however, you need a server up, oauth tokens in place, and an authenticated token for it to work.

queryFetch(`
  self {
    id
    name
  }
`)
.then(console.log)

function queryFetch(query, variables) {
  const YOUR_TOKEN = "add-token-here"
  return fetch('https://api.meetup.com/gql/', {
    method: 'POST',
    headers: { "Content-Type": "application/json", "Authorization": `Bearer ${YOUR_TOKEN}` },
    body: JSON.stringify({
      query: query,
    })
  }).then(res => res.json())
}

Summary of how the api schema works for queries:

1. When you make a request to an object with a type the schema shows fields as required
   note: This does not mean all of them are required you are just required to have a single one of those values present.

2. You need to keep nesting down until the required field is a primitive type or has all fields not required.
   note: If you fail to do this you will get an error and your entire query will not work.

SMH, this does not work client side because gql request is not cors enabled ...