Open paultannenbaum opened 2 years ago
@benkroeger any idea on if this issue is something unique to me, or an actual bug with the repo?
this appears to be an issue with the entitySuffix
property.
Can you (temporarily) work without specifying it?
Also, a PR fixing this is highly welcome
this appears to be an issue with the
entitySuffix
property. Can you (temporarily) work without specifying it? Also, a PR fixing this is highly welcome
Why do you think entitySuffix
is causing this behaviour? Can you show the part of the code that is to blame?
Would like to open a PR fixing it because ive run into the same problem, but as i am new to the codebase I dont even know where the problem is located.
because with en empty entitySuffix
it works as expected :)
generateRelationInput computes the class name without the Entity
suffix while the class is actually generated with a different name
Hi @benkroeger, thanks for replying back to my issue about relations in #14 .
So I just tried your suggestion of adding in the annotated relations, but I am now running into more issues. The
create-${resource}.dto.ts
is being appropriately updated with the new relations, however those relation entities are not being generated themselves. Here is an example:schema.prisma
create-asset.dto.ts
In the above example, the
CreateVenueDtoEntity
andCreateAssetVenueRelationInputDtoEntity
called in the@ApiExtraModels
decorator do not exist/have not been generated, and neither has theCreateAssetVenueRelationInputDtoEntity
found in the DTO definition.Because of this, the TS compiler is failing. Any ideas what is going wrong here?