Strapi 5 - findMany, the type is not populated (COPY)

Discord Q&A strapi-questions
1

I’m still dealing with solving an issue that is really important for my project to progress.

I’m not sure if I’m doing something wrong, or there’s an bug.

I’m trying to findMany & populate. The issue I have is the types are wrongly assinged.


    const collections = await strapi.entityService.findMany("api::device-collection.device-collection", {
      populate: {
        devices: {
          populate: {
            stores: true,
            expertScore: true,
            images: true,
            specification: true
          }
        }
      }
    });

const collections: ContentType<"api::device-collection.device-collection", Schema.NonPopulatableAttributeNames<"api::device-collection.device-collection">>[]

That’s the type I’m getting. Data inside request is populated correctly but the type is totaly wrong.

This topic has been created from a Discord post (1290781593946030100) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord

2

Also, are there any docs for Typescipt types? Cause all I currently do is reverse engineer the whole source code for a manual typing with populate

3

I would suggest you use as temporary, not sure about v5 but in v4 these major types had depth around 3 or 4 levels

4

same issue, I cannot use the strapi.documents document service with filter or fields, since strapi fails to boot, due to some typescript errors…

5

ive resorted back to using the query engine api

6

You’d prolly also should go with as since likely this is going to be fixed at some point

7

And query engine good only for fetching from database…

8

doing this now

 const user_info = await strapi.db.query(API_USER_INFO).create({
                data: {
                    height: 0,
                    user: {
                        // db.query uses the actual id, not the document id
                        connect: [userId]
                    }
                }
            });
9

and doint the filtering in js …

 const user_infos: any = await strapi.documents(API_USER_INFO).findMany({
            populate: '*',
        });

        // only return my user_infos, this should be doable directly via findMany and filters
        const filtered_user_info = user_infos.filter((user_info: any) => user_info.user.id === ctx.state.user.id);

which is not ideal, the database should do this :confused:

10

Well for the second part it should be something like:

const userInfos = await strapi.db.query.findMany({ where: { user: { id: userId } }, populate: … })
11

For the first part, I’ve would recommend using document service (since entity creation isn’t something you want db query for)

12

but isnt the documentService supposed to be “used” and with working filtering?
I was not able to get the documentService to work with create. It always throws some typescript errors. db.query works fine.

13

this filtering works

const user_infos = await strapi.db.query(API_USER_INFO).findMany({
            where: {
                user: {id: ctx.state.user.id}
            }, populate: ['user']
        })

however, its still the db query engine :confused:

14

ok, but with the as typecast, this seems to also work

const user_infos = await strapi.documents(API_USER_INFO).findMany({
            where: {
                user: {id: ctx.state.user.id}
            }, populate: 'user' as Populate.Any<ContentType>
        })
15

doesnt however work for the documents.create api

16

Just put as any after weight)

17

Or @ts-ignore before, ignores are easier to find after they fix the issue