Jean-Sébastien Herbaux

Hey @sepiette, by any chance, do you have a minimal example I could use to reproduce the issue you're having? I fail to break it on my side :confused:

> I'm having this issue as wel. Happening on `strapi develop`. All I did was install Strapi like `npx create-strapi-app@latest strapi-4.3` selected "Typescript" and "Postgres" and ran the develop command....

> This problem goes much deeper. None of the compiled `.ts` files can be found in the dist directory. for example in src/api/model not a single controllers, routes, services directory...

As you rightly mentioned registering the plugins in the `makeSchema` call means that they're going to be registered twice in the end. We've intentionally removed this in this [commit](https://github.com/strapi/strapi/commit/fe4645c385f5ca7f9ddca4105526561d56b59287) >...

Hey @edvincandon, thanks for the reply and sorry for the late answer. Indeed it could be a simple solution to this issue. I'm just concerned it won't be as straightforward...

IMO it doesn't really matter which "core" squad is handling this. It's one of those shared subjects that anyone could take. Everyone's using those utils and contributing to them :shrug:

Hello there, > @Convly I disagree with you. Whilst anyone can contribute, you can't contribute if you don't know how things work. I am a Strapi user, not a Strapi...

Hey, is the issue the fact that you've to add a `publicationState: LIVE` to the relation attributes too? If it's that, then it's the wanted behavior as we don't cascade...

Indeed. In V3 we were sharing the state to child resolvers but it didn't really make sense in a GraphQL architecture where every resolver should be as isolated as possible....

We might need to update the frontend snapshots @simotae14. Do you think you can take some time for this?