Best practice accessing populated fields in Strapi4 response

Hello 😃

I was just playing around and saw that populated fields are returned with the same structure as the “parent”

   export interface Strapi4ResponseData<T> {
     id: number,
     attributes: T,
     meta: Record<string, unknown>
   }

Accessing such a field would result in response.data[0].attributes.populated_field.data.attributes

In my case, I populated a media field containing one picture.

Quite the difference from the Strapi3 response.

What would you recommend in terms of storing such a response in store (I’m currently using pinia) and accessing the data as efficient as possible?

[benjamincanac]

Closing this as I dont have any more informations on how to achieve this.

@luke-z If you feel your solution is ready, don’t hesitate to make a PR to the documentation in Advanced section to explain how to achieve this, maybe the solution described here https://github.com/nuxt-community/strapi-module/issues/204 can be usefull too.

[jch-code]

I created a tool to handle this issue for myself, strapi-parse.

I have only used it on a small sample size in my own projects, so I wouldn’t be surprised if I missed some edge cases, but it works for me on some fairly complex objects with populated fields, dynamic zones, & repeatable components.