Aller au contenu
uencoder

Comment en Convertir Entre Naming Conventions

Transformer identifiers entre camelCase, snake_case, kebab-case, PascalCase, et SCREAMING_SNAKE_CASE.

问题

Your code uses one naming convention mais un library ou style guide requires another.

Prérequis

  • Knowledge of programming naming conventions
  • Understanding of word boundaries

Étapes

  1. 1. Identify source and target conventions

    Determine the current convention (e.g., camelCase) and the target (e.g., snake_case). Common conventions include camelCase, PascalCase, snake_case, kebab-case, and SCREAMING_SNAKE_CASE. Each language has preferred conventions.

    entrée
    source: camelCase → target: snake_case
    输出
    conventions set
  2. 2. Parse the identifier into words

    Split the identifier at word boundaries. For camelCase/PascalCase, boundaries are at capital letters. For snake_case/kebab-case, boundaries are at underscores/hyphens. Handle acronyms and consecutive capitals carefully.

    entrée
    myXMLParser
    输出
    words: [my, XML, Parser]
  3. 3. Reassemble in the target convention

    Join the words using the target convention's rules. For snake_case, lowercase all words and join with _. For PascalCase, capitalize each word and concatenate. For SCREAMING_SNAKE, uppercase and join with _.

    entrée
    words + target: snake_case
    输出
    my_xml_parser

Résultat attendu

Le identifier correctly converted en le target naming convention.

Erreurs courantes

Acronym casing lost
Some conventions preserve acronym casing (myXMLHandler not myXmlHandler). Configure the converter's acronym handling.
Leading/trailing separators
Ensure the output does not start or end with a separator (_ or -) unless the input did.

Dépannage指引

  • If the output is wrong, check the word splitting step.
  • Test with edge cases: single word, all caps, numbers, mixed separators.

Limites de sécurité

  • Naming convention conversion is a text transformation with no security implications.

Outils associés

参考链接