Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Should file import be case sensitive?
See original GitHub issuee.g. tree.GLTF does not work, says “no .gltf asset found”.
If a buffer references “foo.bin” but the file is actually “foo.BIN”, that’s also unsupported, but less surprising.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How case-sensitive should file extensions be? #2730 - GitHub
But extensions is case insensitivity. Is this generally true? According to whom? If we were to declare that Sass extensions were universally ...
Read more >Case-sensitive import statements in TypeScript
It turns out that import statements are case-insensitive on Mac and Windows but case-sensitive on Linux. There is a ...
Read more >PEP 235 – Import on Case-Insensitive Platforms
NONE OF THAT IS CHANGING ! Python will continue to follow platform conventions w.r.t. whether case is preserved when creating a file, and...
Read more >Proc Import - case sensitivity in filename - SAS Communities
No. You could ask the operating system to give you list of all of the files and then pick the one you think...
Read more >Adjust case sensitivity - WSL - Microsoft Learn
Windows file system treats file and directory names as case-insensitive. FOO.txt and foo.txt will be treated as equivalent files. Linux file ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The spec refers to RFC 3986, which defines URIs as case-sensitive.
That’s an interesting point. At least on *nix OSes,
url: "IMAGE.png"andurl: "image.png"will refer to different files - even though they could not be distinguished on Windows, and thus, the glTF would not be “platform independent” if it contained both. (From the tip of my head, I cannot say whether the spec says anything here…)