TypeScript consistent casing
User guide
- Getting Started
Api
Concepts
Configurations
Configuring webhint
Connectors
Development flow integration
Extensions
Formatters
Hints
- Avoid CSS limits
- Avoid HTTP redirects
- axe accessibility check
- Babel configuration hint set
- Compatibility of CSS, HTML and JavaScript features
- Correct `Content-Type` header
- Correct manifest extension
- Correct viewport
- Detect CSS Reflows
- Disallowed HTTP headers
- External links disown opener
- Has web app manifest
- Highest document mode
- HTTP cache
- Leading '.' in `classList.add` or `classList.remove`
- Manifest has name
- Minify JavaScript
- Modern DOCTYPE
- No `createElement` with SVG
- No `P3P` headers
- No broken links
- No byte-order mark
- No Inline CSS Styles
- No protocol-relative URLs
- No small error pages
- No vulnerable libraries
- Nu HTML test
- Optimal compression
- Optimize images
- Performance budget
- Prefixed CSS first
- scoped-svg-styles
- Specify button type
- SSL server test
- TypeScript configuration hints set
- Unneeded HTTP headers
- Use `Strict-Transport-Security` header
- Use `X-Content-Type-Options` header
- Use Apple touch icon
- Use charset `utf-8`
- Use HTTPS
- Use subresource integrity
- Valid `Set-Cookie` header
- Valid `theme-color`
- Valid manifest
- webpack configuration hints set
Parsers
Server configurations
Troubleshoot
- Api
- Concepts
- Configurations
- Configuring webhint
- Connectors
- Development flow integration
- Extensions
- Formatters
- Hints
- Parsers
- Server configurations
- Troubleshoot
TypeScript consistent casing (consistent-casing
)
typescript-config/consistent-casing
checks if the property forceConsistentCasingInFileNames
is enabled in your TypeScript configuration file (i.e. tsconfig.json
).
Why is this important?
If you are working on a project where developers use different OSes (e.g.: Windows and Linux), enabling this property will prevent issues related to the file casing and how the files are referenced in the code.
What does the hint check?
This hint checks if the compilerOptions
property forceConsistentCasingInFileNames
is enabled.
Examples that trigger the hint
By default, TypeScript doesn’t enforce this:
{
...
"compilerOptions": {
"target": "es5",
...
},
...
} |
Also setting the value to false
will fail:
{
...
"compilerOptions": {
"forceConsistentCasingInFileNames": false,
...
},
...
} |
Examples that pass the hint
forceConsistentCasingInFileNames
value is true
:
{
"compilerOptions": {
"forceConsistentCasingInFileNames": true,
...
},
...
} |