You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, firstly I would like to say thank you for this amazing package. It saved a lot of time for me. Because I am using it currently, I would like to suggest/request two features.
1: Don't override if file exists
When it is generated, sometimes we do changes such as adding validator decorators. Especially when I use outputToNestJsResourceStructure = "true", I do add validators. It would be good if this package does not do anything if there is any file on that location. ( as an option )
2: Select what is going to be generated. For example only generate Entity and Create Dto
The text was updated successfully, but these errors were encountered:
not overriding existing files could lead to inconsistent behaviour. esp. when we import that existing file in another newly generated file to reuse its generated contents.
What I found to work great for me is to have generators produce code in a separate folder (e.g. src/generated) and import DTOs in my nest modules:
This way you can always generate all the things - and only import what you need - and even make modifications.
Also see MappedTypes if you want to exclude generated props or merge classes
Hello, firstly I would like to say thank you for this amazing package. It saved a lot of time for me. Because I am using it currently, I would like to suggest/request two features.
1: Don't override if file exists
outputToNestJsResourceStructure = "true"
, I do add validators. It would be good if this package does not do anything if there is any file on that location. ( as an option )2: Select what is going to be generated. For example only generate Entity and Create Dto
The text was updated successfully, but these errors were encountered: