Field missing in API response for components in related content type

[MatthewSbar]

Describe the bug
The bug is described here https://github.com/strapi/strapi/discussions/5769, but that issue was converted to a discussion despite it being a bug which has not been fixed.

Essentially, when getting data for a content type which has a relation to another content type, fields for components in the related content type are not returned in the API response. Fields which aren't nested in components are included.

Steps to reproduce the behavior

1. Create a content type called Slide
2. Add a component to Slide called images
3. Add a field named imageUrl to the images component
4. Create two slides with different images
5. Create a content type called Landing Page
6. Add a repeatable component called slideshow to Landing Page
7. Add a one-to-one relation to Slides in the slideshow component
8. Create a landing page
9. Add both slides to the landing page
10. Navigate to /landing-pages to fetch the data for landing pages
11. In the response, the slides are included, but the images component is not included

Expected behavior
In step 11, the images field would be included.

System

Node.js version: 12.14.1
NPM version: 6.13.4
Strapi version: Strapi v3.0.0
Database: Postgres
Operating system: ubuntu 18.04.04 lts

[derrickmehaffy]

I can confirm this, I've included a test project:
test7360.zip

[rowdyrabouw]

The same happens in your example of creating a menu (https://www.youtube.com/watch?v=cvL204xus1w). You don’t get the dropdown items returned (label + link), only a reference to the dropdown. The dropdown is a component.

[derrickmehaffy]

related: #7454

[pk0gler]

And how exaclty can you fix this right know.
Is there any way i can come around this.
https://www.youtube.com/watch?v=VBNjCgUokLk&list=PL7Q0DQYATmvhlHxHqfKHsr-zFls2mIVTi&index=17&t=0s
this video shows how to extend populate behaviour of a content type.

How would you achieve this in a component with a relation?

[derrickmehaffy]

@pkogler-tgm we don't currently have a fix at the moment

[Stun3R]

I had the same problem just after migrating from v3.0.2 to v3.2.4. I tried to downgrade to 3.1.7 and finally it worked to populate with component !

[a1tem]

Hi guys is there any solution? I have faced the same issue with components in the hasOne relation. We do need to populate the component data, in order to avoid making a new query.