Closed EsGeh closed 1 year ago
Thank you for reporting the issue, yes it is looking for a content type for each api (which is incorrect, but works for basic setups). I think the fix is relatively easy, although I am not really working on this project right now. I will look at it if i get time, else I will be glad to review a PR.
I am working on this now fyi, should be done this week
When adding a custom to strapi, as defined in the strapi docs, type generation will fail with an ugly exception:
How to reproduce:
As described in the strapi docs, add 2 files like:
/src/api/hello/routes/hello.ts:
./src/api/hello/controllers/hello.ts
Maybe that is, because t4s expects
./scr/api/hello/
to contain acontent-types/
dir containing someschema.json
(?)