What is the actual issue you're seeing? I dont directly see anything wrong with that generated type but is always hard to tell without the appropriate context.

What is the actual issue you're seeing? I dont directly see anything wrong with that generated type but is always hard to tell without the appropriate context.

The TypeScript issue I'm facing involves incorrect type resolution for queries. Ideally, only the queried fields should be resolved, but instead, it resolves the entire object type from the collection, when filtering additionally with _and/_or filters.

Edit: The first example is showing a correct example. The second the kinda buggy one.

Mind sharing the important parts of the schema for reproduction too? the root and product types should do.

Maybe this ticket is connected with the following issue? #19285

If not related to the issue it will be related to the PR as thats where these conditionals were implemented

I uploaded a test repo here https://github.com/sensedrive/directus-types-test

Filtering with or without _and makes a significant difference in the response types.

You should see an ts errror in line 16. Or I am doing something wrong ...

I face a similar problem.
I'm using nextjs. I see using chatGPT the problem could be in ts config : "moduleResolution": "bundler",
But this is the next config and don't want to change it.

Actually what i run into is when i want to filter a readItems the filter couldn't be partial.
I mean i just want to filter by Slug like this:

export const findServiceBySlug = async (slug: string) => {
  const service = await directus.request(
    readItems("service", {
      fields: ["*", { fimg: ["*"] }, { block_image: ["*"] }],
      filter: { slug: { _eq: slug } },
      limit: 1,
    })
  );

And ts throw this error underlining the world filter:

Type '{ slug: { _eq: string; }; }' doesn't have properties of type 'QueryFilter<ISchema, IService>': id, name, subtitle, price and 8 more.ts(2740)
(property) Query<ISchema, IService>.filter?: QueryFilter<ISchema, IService> | undefined

@sensedrive The only solution I find for now is using //ts-ignore