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
The "Move to a new file" refactor is a great tool, except that the generated file keeps the casing of whatever you are moving.
Example:
exportinterfaceUserSettings{language: string;}
Using the refactor here creates a file named "UserSettings.ts" (PascalCase) while I would like it to be named "user-settings.ts" (kebab-case)
A setting to change this behavior with options like:
Keep case of class/interface/etc name (current behavior)
Convert to PascalCase
Convert to kebab-case
Convert to lower case
(plus snake_case and camelCase i guess)
would remove an extra step (renaming the generated files or creating files by hand and manually importing it) and would make me and at least one other person on stack overflow very happy.
The text was updated successfully, but these errors were encountered:
Letting users explicitly specify the file name (#50685) would address this. If we add an explicit set of options for the name, we could keep adding new options forever and never make everyone happy
The "Move to a new file" refactor is a great tool, except that the generated file keeps the casing of whatever you are moving.
Example:
Using the refactor here creates a file named "UserSettings.ts" (PascalCase) while I would like it to be named "user-settings.ts" (kebab-case)
A setting to change this behavior with options like:
would remove an extra step (renaming the generated files or creating files by hand and manually importing it) and would make me and at least one other person on stack overflow very happy.
The text was updated successfully, but these errors were encountered: