-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add configuration option to generate files with PascalCase instead of the default naming convention #462
Comments
Side-demand. It would be nice to also support naming test files with |
We're tracking this here nestjs/schematics#143 |
If a Should there also be introduced a Something like https://www.npmjs.com/package/change-case could help implement the solution without having to worry about correct case convertions |
this would be a very nice addition. having to switch to kabob case is a huge pain for our team |
Is there any news on this? |
Is there any news on this?( |
Is there any news on this? Do you need any help? |
Contributions are more than welcome! @hydra13 |
Hi, is this issue still on going? I need this feature (with camelcase) and want to take a look if it's still valid. @kamilmysliwiec |
@kamilmysliwiec can you point me to the code which generates the files? I want to try implementing support for file names in PascalCase. 🙂 |
@bennycode |
I started working on a draft PR for this feature. @kamilmysliwiec or @micalevisk I would love some feedback! |
Let's track this here #2208 |
I'm submitting a...
Current behavior
As of now, if I generate a new file with
nest g
, its is namedname.type.ts
(e.g.my.module.ts
).I'd like the tool to create a file named
NameType.ts
(e.g.MyModule.ts
) so that it matches the name of the class it contains.Expected behavior
Ideally, a
fileNameCase
configuration option innest-cli.json
of type"dot" | "pascal" | "camel" | "snake" | "kebab"
would be nice.Minimal reproduction of the problem with instructions
nest g mo my
generates a file namedmy.module.ts
What is the motivation / use case for changing the behavior?
All of my company source files are named with the same name as the classes that they include. It's a common convention we see in a lot of OOP projects.
The text was updated successfully, but these errors were encountered: