Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

camelCase misspelled in pt-br documentation #44093

Open
JoaoVictorGI opened this issue Dec 27, 2024 · 3 comments
Open

camelCase misspelled in pt-br documentation #44093

JoaoVictorGI opened this issue Dec 27, 2024 · 3 comments
Labels
dotnet-csharp/svc fundamentals/subsvc loc Indicates issues that are about localized content [org][type][category]

Comments

@JoaoVictorGI
Copy link

JoaoVictorGI commented Dec 27, 2024

Type of issue

Typo

Description

Convenções de nomenclatura
Além das regras, as convenções para nomes de identificador são usadas em todas as APIs do .NET. Essas convenções fornecem consistência para nomes, mas o compilador não as impõe. Você é livre para usar convenções diferentes em seus projetos.

Por convenção, os programas C# usam PascalCase para nomes de tipo, namespaces e todos os membros públicos. Além disso, a equipe dotnet/docs usa as seguintes convenções, adotadas a partir do estilo de codificação da equipe do .NET Runtime:

Os nomes de interface começam com I maiúsculo.

Os tipos de atributo terminam com a palavra Attribute.

Os tipos enumerados usam um substantivo singular para nonflags e um substantivo plural para sinalizadores.

Os identificadores não devem conter dois caracteres de sublinhado (_) consecutivos. Esses nomes estão reservados para identificadores gerados por compilador.

Use nomes significativos e descritivos para variáveis, métodos e classes.

Prefira clareza em vez de brevidade.

Use PascalCase para nomes de classe e nomes de método.

Use ❗ CamelCase ❗ para parâmetros de método e variáveis locais.

Use PascalCase para nomes de constantes, tanto para constantes de campo quanto para constantes de local.

Os campos de instância privada começam com um sublinhado (_) e o texto restante usa ❗ CamelCase ❗.

Page URL

https://learn.microsoft.com/pt-br/dotnet/csharp/fundamentals/coding-style/identifier-names

Content source URL

https://github.com/dotnet/docs/blob/main/docs/csharp/fundamentals/coding-style/identifier-names.md

Document Version Independent Id

7f85babc-6295-21dd-f194-dede663f9966

Article author

@BillWagner

Metadata

  • ID: a2d591be-290e-62d1-e99a-a7d26af20ef8
  • Service: dotnet-csharp
  • Sub-service: fundamentals

Related Issues

@BillWagner
Copy link
Member

Hi @JoaoVictorGI

It looks like this issue primarily restates what's in the article. Is there more information you need from this article?

@BillWagner BillWagner added needs-more-info Needs more info from OP. Auto-closed after 2 weeks if no response. [org][resolution] and removed ⌚ Not Triaged Not triaged labels Jan 6, 2025
@gewarren gewarren added loc Indicates issues that are about localized content [org][type][category] and removed needs-more-info Needs more info from OP. Auto-closed after 2 weeks if no response. [org][resolution] labels Jan 8, 2025
@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Jan 8, 2025
@gewarren
Copy link
Contributor

gewarren commented Jan 8, 2025

@BillWagner The title describes the problem. CamelCase should be spelled camelCase.

@BillWagner
Copy link
Member

Thanks for the clarifications.

I've reported this to the loc team on their internal tracking system.

@BillWagner BillWagner removed the ⌚ Not Triaged Not triaged label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dotnet-csharp/svc fundamentals/subsvc loc Indicates issues that are about localized content [org][type][category]
Projects
None yet
Development

No branches or pull requests

4 participants