Mongoose query with unprojection on dynamic zone field causes error

[atlmtw]

Describe the bug
When creating a custom controller on a content type that has a dynamic zone field, excluding it from the selection of the query causes an error (Mongoose). For instance lets say we have dynamic zone field called "modules".

If my query looks like this:

strapi.query("name")
  .model
  .find({},{modules:0}); <-- Excluding it from selection through field projection

Then it causes an error with the strapi-mongoose-connector library. If I don't include "modules" in it, it works. If I try to unproject another field that is not a dynamic zone field, it works.

My custom controller code looks like this:

The error message I get is in this screen shot:

It appears that the library is still trying to map on the dynamic zone field despite it not being in the returned query.

Expected behavior
It should return all objects that match the query of the controller without the "modules" dynamic zone field.

System

• Node.js version: v12.16.2
• NPM version: 6.14.4
• Strapi version: 3.0.0-beta.20.1
• Database: MongoDB 4.2.6
• Operating system: Ubuntu 18.04 LTS

Thanks again and as always I appreciate the work the Strapi team does!

[lauriejim]

Thank you for reporting this issue, I ping @alexandrebodin about that.

[alexandrebodin]

Hi @atlmtw There is an automatic population of dynamic zones hence the code running. It is a pretty easy fix to check if there is data before trying to process it. A good first PR if you want ;)

[atlmtw]

Hey @alexandrebodin! Maybe ill try it out later tonight and submit a PR.

[alexandrebodin]

Closing as #6916 was merged. It will be available in the next release :)