Naming strategy similar to PropertyNamingStrategies.SnakeCaseStrategy, but instead of underscores as separators, uses hyphens. Naming convention traditionally used for languages like Lisp.

"No-operation" strategy that is equivalent to not specifying any strategy: will simply return suggested standard bean naming as-is.

Simple strategy where external name simply only uses lower-case characters, and no separators. Conversion from internal name like "someOtherValue" would be into external name if "someothervalue".

Naming strategy similar to PropertyNamingStrategies.KebabCaseStrategy, but instead of hyphens as separators, uses dots. Naming convention widely used as configuration properties name.

Intermediate base class for simple implementations

A PropertyNamingStrategy that translates typical camel case Java property names to lower case JSON element names, separated by underscores. This implementation is somewhat lenient, in that it provides some additional translations beyond strictly translating from camel case only. In particular, the following translations are applied by this PropertyNamingStrategy.

• Every upper case letter in the Java property name is translated into two characters, an underscore and the lower case equivalent of the target character, with three exceptions.
  1. For contiguous sequences of upper case letters, characters after the first character are replaced only by their lower case equivalent, and are not preceded by an underscore.
     • This provides for reasonable translations of upper case acronyms, e.g., "theWWW" is translated to "the_www".
  2. An upper case character in the first position of the Java property name is not preceded by an underscore character, and is translated only to its lower case equivalent.
     • For example, "Results" is translated to "results", and not to "_results".
  3. An upper case character in the Java property name that is already preceded by an underscore character is translated only to its lower case equivalent, and is not preceded by an additional underscore.
     • For example, "user_Name" is translated to "user_name", and not to "user__name" (with two underscore characters).
• If the Java property name starts with an underscore, then that underscore is not included in the translated name, unless the Java property name is just one character in length, i.e., it is the underscore character. This applies only to the first character of the Java property name.

These rules result in the following additional example translations from Java property names to JSON element names.

• "userName" is translated to "user_name"
• "UserName" is translated to "user_name"
• "USER_NAME" is translated to "user_name"
• "user_name" is translated to "user_name" (unchanged)
• "user" is translated to "user" (unchanged)
• "User" is translated to "user"
• "USER" is translated to "user"
• "_user" is translated to "user"
• "_User" is translated to "user"
• "__user" is translated to "_user" (the first of two underscores was removed)
• "user__name" is translated to "user__name" (unchanged, with two underscores)

A PropertyNamingStrategy that translates typical camelCase Java property names to PascalCase JSON element names (i.e., with a capital first letter). In particular, the following translations are applied by this PropertyNamingStrategy.

• The first lower-case letter in the Java property name is translated into its equivalent upper-case representation.

This rules result in the following example translation from Java property names to JSON element names.

• "userName" is translated to "UserName"

A PropertyNamingStrategy that translates an input to the equivalent upper case snake case. The class extends PropertyNamingStrategies.SnakeCaseStrategy to retain the snake case conversion functionality offered by the strategy.