[FIX] strapi-v4 - data provider - deep data normalization

Is your feature request related to a problem? Please describe. Populated data from strapi-v4 data provider are not normalized, which makes hard to work with them via ts interfaces.

Describe the solution you’d like Use deep traversal like the one proposed here : https://forum.strapi.io/t/discussion-regarding-the-complex-response-structure-for-rest-graphql-developer-experience/13400/9

const normalize = (data) => {
  const isObject = (data) =>
    Object.prototype.toString.call(data) === '[object Object]'
  const isArray = (data) =>
    Object.prototype.toString.call(data) === '[object Array]'

  const flatten = (data) => {
    if (!data.attributes) return data

    return {
      id: data.id,
      ...data.attributes
    }
  }

  if (isArray(data)) {
    return data.map((item) => normalize(item))
  }

  if (isObject(data)) {
    if (isArray(data.data)) {
      data = [...data.data]
    } else if (isObject(data.data)) {
      data = flatten({ ...data.data })
    } else if (data.data === null) {
      data = null
    } else {
      data = flatten(data)
    }

    for (const key in data) {
      data[key] = normalize(data[key])
    }

    return data
  }

  return data
}

Describe alternatives you’ve considered Alternative would be to normalize data after you get query data. This might be too late if you load it as useTable which expect slightly modified data already.

Additional context Read more at : https://forum.strapi.io/t/discussion-regarding-the-complex-response-structure-for-rest-graphql-developer-experience/13400

[salihozdemir]

Hey @lukassos 👋 ,

Thanks for your contribution. After this point, we will make a new release by making additions to what you have done. When finished, we would appreciate it if you could review the changes and make sure they are correct.

[omeraplak]

Hey @lukassos , I forgot we already normalized data. Thanks a lot for your warning. Now everything is clearer to me. Thanks so much for your passion!

What we have to do now is

• Fixing tests (I’ll do that)
• Updating our documentation

You can create a new section for the document. I’ll also try to set the “plugin::users-permissions.user” plugin today as you suggested. Is there anything I missed?