Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Change abbreviation guideline

Abierto
#204 3 comentarios 0 reacciones 2 asignados Ver en GitHub

@joeriddles ya está trabajando en esto.

Desde el 29/12/2021.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

proposal

Currently we have separate rules for abbreviations and acronyms. This proposal brings those together into single rules. The existing rules do not match which what most code does with well-known abbreviations such as: ID (Identifier), Company abbreviations, DB (Database), TM (Trademark), Cert (Certificate), Sig (Signature), etc.

Proposal: Change the following guidelines:

❌ DO NOT use abbreviations or contractions within identifier names.
❌ DO NOT use any acronyms unless they are widely accepted, and even then use them consistently.
✔️ DO capitalize both characters in two-character acronyms, except for the first word of a camelCased identifier.
✔️ DO capitalize only the first character in acronyms with three or more characters, except for the first word of a camelCased identifier.
❌ DO NOT capitalize any of the characters in acronyms at the beginning of a camelCased identifier.

To be:

❌ DO NOT use contractions within identifier names.
⛔ AVOID use any acronyms or abbreviations unless they are widely accepted, and even then, use them consistently.
✔️ DO capitalize only the first character in acronyms or abbreviations with two or more characters, except for the first word of a camelCased identifier.
❌ DO NOT capitalize any of the characters in acronyms or abbreviations at the beginning of a camelCased identifier.

Lenguaje dominante
C#
Estrellas
12
Forks
16
Merge medio
2 min
PR fusionados (30 d)
7

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de IntelliTect/CodingGuidelines

Todos los issues de IntelliTect/CodingGuidelines

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.