You do not need a regular expression for that. var yourString = “WARD_VS_VITAL_SIGNS”.ToLower().Replace(“_”, ” “); TextInfo info = CultureInfo.CurrentCulture.TextInfo; yourString = info.ToTitleCase(yourString).Replace(” “, string.Empty); Console.WriteLine(yourString);
See Python PEP 8: Function and Variable Names: Function names should be lowercase, with words separated by underscores as necessary to improve readability. Variable names follow the same convention as function names. mixedCase is allowed only in contexts where that’s already the prevailing style (e.g. threading.py), to retain backwards compatibility.
([A-Z][a-z0-9]+)+ Assuming English. Use appropriate character classes if you want it internationalizable. This will match words such as “This”. If you want to only match words with at least two capitals, just use ([A-Z][a-z0-9]+){2,} UPDATE: As I mentioned in a comment, a better version is: [A-Z]([A-Z0-9]*[a-z][a-z0-9]*[A-Z]|[a-z0-9]*[A-Z][A-Z0-9]*[a-z])[A-Za-z0-9]* It matches strings that start with an uppercase letter, … Read more
I made this a while ago. It matches each component of a CamelCase name. /([A-Z]+(?=$|[A-Z][a-z])|[A-Z]?[a-z]+)/g For example: “SimpleHTTPServer” => [“Simple”, “HTTP”, “Server”] “camelCase” => [“camel”, “Case”] To convert that to just insert spaces between the words: Regex.Replace(s, “([a-z](?=[A-Z])|[A-Z](?=[A-Z][a-z]))”, “$1 “) If you need to handle digits: /([A-Z]+(?=$|[A-Z][a-z]|[0-9])|[A-Z]?[a-z]+|[0-9]+)/g Regex.Replace(s,”([a-z](?=[A-Z]|[0-9])|[A-Z](?=[A-Z][a-z]|[0-9])|[0-9](?=[^0-9]))”,”$1 “)
A shorter solution: Similar to the editor’s one with a simplified regular expression and fixing the “trailing-underscore” problem: $output = strtolower(preg_replace(‘/(?<!^)[A-Z]/’, ‘_$0’, $input)); PHP Demo | Regex Demo Note that cases like SimpleXML will be converted to simple_x_m_l using the above solution. That can also be considered a wrong usage of camel case notation (correct … Read more
This works with your testcases: static String splitCamelCase(String s) { return s.replaceAll( String.format(“%s|%s|%s”, “(?<=[A-Z])(?=[A-Z][a-z])”, “(?<=[^A-Z])(?=[A-Z])”, “(?<=[A-Za-z])(?=[^A-Za-z])” ), ” ” ); } Here’s a test harness: String[] tests = { “lowercase”, // [lowercase] “Class”, // [Class] “MyClass”, // [My Class] “HTML”, // [HTML] “PDFLoader”, // [PDF Loader] “AString”, // [A String] “SimpleXMLParser”, // [Simple XML Parser] … Read more
In this document Google JSON Style Guide (recommendations for building JSON APIs at Google), It recommends that: Property names must be camelCased, ASCII strings. The first character must be a letter, an underscore (_), or a dollar sign ($). Example: { “thisPropertyIsAnIdentifier”: “identifier value” } My team consistently follows this convention when building REST APIs. … Read more