Empty Content Collections with defined scema don't generate typescript types about astro HOT 7 OPEN

Are you saying that the reproduction doesn't show the issue you found?

from astro.

Massive egg on my face, but yes. I tried to get it to break yesterday but just couldn't. I am however able to do it with the project I'm working on, I can make the repository public so you can poke around if you like.

from astro.

Unless it's relatively small would prefer that you reproduce in the example you provided. It's possible that through reducing you'll find out that it's not a bug at all.

from astro.

I had to poke it a bit, but I reproduced the issue. Turns out, it's not a problem with the build like I thought, it's a problem with astro check

Reproduction steps are load up the codespace, run astro check, and observe it freak out when the collection's empty

from astro.

astro check's behaviour is correct here - when the collection is empty the types are unknown, never etc so trying to do operations on them results in type errors.

from astro.

astro check's behaviour is correct here - when the collection is empty the types are unknown, never etc so trying to do operations on them results in type errors.

That would make sense if a collection didn't have a schema defined, but since it does the type would be known in theory, I would think

from astro.

@murl-digital Ah interesting, I am able to replicate with your Stackblitz example by running npm run astro check. Confirmed the issue goes away if at least one entry is present. I agree we should defer to your config types when a directory is empty

from astro.