Add names to Enums #52
Comments
|
|
|
Thanks! |
Brakebein
added a commit
that referenced
this issue
Sep 30, 2024
ablyeom
added a commit
to ablyeom/prisma-generator-nestjs-dto
that referenced
this issue
Jan 21, 2025
* brakebein/main: version 1.24.1 fix Decimal type definition Brakebein#63 version 1.24.0 update readme deprecate outputApiPropertyType fix @DtoRelationRequired Brakebein#54 change DtoApiOverrideType to DtoOverrideApiPropertyType Brakebein#54 fix encapsulateString for null Brakebein#58 fix encapsulateString for date strings Brakebein#58 add @DtoCreateRequired decorator Brakebein#55 replace DtoCastType with DtoOverrrideType Brakebein#54 fix don't generate enums.ts if there are no enums defined add flag to show fields with default attribute by default Brakebein#51 add enumName to ApiProperty Brakebein#52 generate enums if noDependencies = true Brakebein#48 wrap relations as type to fix circular dependencies Brakebein#49 shorten duplicate code checks on double imports sort all imports shorten duplicate code to make class-validator imports fix ApiProperty default value if field is a list
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
According to that, for reusable enum generation (which would fix generating tons of exactly-the-same-not-compatible-with-eachother-enums on frontend), we need to add
enumNameproperty toApiProperty. I think we can do it now fairly easily, because the name of enums could match import exactly. Otherwise, on every route there's a new enum and its literally unusablep.s. I wonder what should I do to contribute? What's the process? @Brakebein
The text was updated successfully, but these errors were encountered: