NEW ANSWER FOR TYPESCRIPT 4.1+ Welcome back! Now that TypeScript 4.1 has introduced template literal types and the Uppercase/Lowercase intrinsic string mapping types, we can now answer this question without needing regular expression types. There are two main approaches. The “brute force” approach makes heavy use of recursive conditional types and unions to turn your … Read more
Use String.Equals with the appropriate parameters to make it case insensitive mySource.Where(s => String.Equals(s, “Foo”, StringComparison.CurrentCultureIgnoreCase));
Use Rename option in Tortoise SVN from popup menu. See details here (“Moving files and folders” chapter). When you changed the case of several file names, in other words you changed file names – they have become out of version control – that’s why SVN client noticed that files that was under version control had … Read more
You must use ~* instead of ~.
I am not aware of any differences other than personal preference. Personally, I prefer lowercase since it’s quicker to read, although in very short strings such as CSS color values, the benefit is probably negligible. Really, I think it’s just because I think lowercase looks better. Hexadecimal, however, is traditionally written in uppercase, so maybe … Read more
Having [NC] is definitely not mandatory but it is recommended to have it for matching domains. Modern browsers might be converting domain names to lowercase but what about old browsers and command line utils like wget, curl etc, so you should not always rely on clients sending you lowercase domain name and keep [NC]. About … Read more
[Here is the result of my research.] RFC 2616 clause 3.4 says the following: HTTP character sets are identified by case-insensitive tokens. The complete set of tokens is defined by the IANA Character Set registry [19]. charset = token The IANA Character Set registry is now maintained here. At the very top of this document … Read more