Any reason for not using forceConsistentCasingInFileNames ? #38
Closed
scr2em
started this conversation in
TypeScript Suggestion
Replies: 1 comment 1 reply
-
Absolutely. Would you like to make a PR for this? Could you include a decision document in the PR as well? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Search Terms Used
force
consistent
casing
file
names
forceConsistentCasingInFileNames
Config Docs
https://www.typescriptlang.org/tsconfig/#forceConsistentCasingInFileNames
Suggested Change
add forceConsistentCasingInFileNames in typescript config
Issues without the change
TypeScript follows the case sensitivity rules of the file system it’s running on. This can be problematic if some developers are working in a case-sensitive file system and others aren’t. If a file attempts to import fileManager.ts by specifying ./FileManager.ts the file will be found in a case-insensitive file system, but not on a case-sensitive file system.
When this option is set, TypeScript will issue an error if a program tries to include a file by a casing different from the casing on disk.
Severity of inaction
low
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions