[Feat] strapi v4 with graphql

Describe the bug I suspect there is a bug, but not sure.

strapi v3 graphql query

query {
  users {
    username
    email
  }
}

strapi v4 graphql query, the field nested under attributes

query {
  documents {
    data {
      id
      attributes {
        title
        categories {
          data {
            id
            attributes {
                name
            }
          }
        }
      }
    }
    meta {
      pagination {
        page
        pageSize
        total
        pageCount
      }
    }
  }
}

In refine, it will query like this:

{
  "query": "query ($where: JSON, $sort: String, $start: Int, $limit: Int) { symptomsConnection (where: $where) { aggregate { count } } symptoms (sort: $sort, where: $where, start: $start, limit: $limit) { name } }",
  "variables": {
    "where": {},
    "sort": "id:asc",
    "start": 0,
    "limit": 10
  }
}

1. Does the symptoms { name } seems use strapi v3 graphql grammer?
2. There are also error messages on request :

...
"Cannot query field \"symptomsConnection\" on type \"Query\"."
...
"Unknown argument \"where\" on field \"Query.symptoms\"."
...

Do I missing something? Or @pankod/refine-strapi-graphql is used for strapi V3?

deps “@pankod/refine-strapi-graphql”: “3.25.6”, “@pankod/refine-strapi-v4”: “3.25.6”,

backend deps “@strapi/plugin-graphql”: “4.2.0”, “@strapi/strapi”: “4.2.0”,

[HaveF]

After some research, except for some technical issues, I find the support to v4 graphql support should be delay.

Lots of complains are found in strapi forum. I guess there would be some changes in the future.

And some technical issues includes:

• strapi-v4 's normalizeData function could handle response problems
• but query problems(mess data, attributes) are hard to resolve

@omeraplak close this issue or just leave it to wait?

[omeraplak]

Spent 2 hours before realizing I needed version 3 of strapi

Sorry to hear that. We should clearly state this in our documents