blocks|key|2754034|text|根据属性的语义为其命名。坦率地说，在一个地址上有一个Person属性是很奇怪的--通常情况下是相反的。这里的人是什么意思？地址和人之间有什么联系？例如，您可能有Owner或Resident+-但在其他情况下，这并不合适。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2754035|entityMap^0|28|5|2E|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Name the property according to its semantic meaning. Frankly it's quite odd to have a Person property on an address - it would normally be the other way round. What's the meaning of the person here? What's the association between the address and the person? You might have <code>Owner</code> or <code>Resident</code>, for example - but in other cases that wouldn't be appropriate.

blocks|key|2754125|text|我会根据这两种类型之间的关系来命名属性，例如，Resident、Owner等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2754126|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I would name the property from the relationship between the two types, e.g. Resident, Owner etc.

blocks|key|4162424|text|我不认为有一个硬性的规则，但总的来说，我喜欢尽可能地坚持以下指导原则：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4162425|4162426|不要重复类的名称。这个问题可能很难解决，但通常可以通过认真考虑第二个规则来解决：|unordered-list-item|4162427|考虑属性在类中的角色，而不仅仅是它是什么。在您的示例中，由于Owner拥有特定的Address.|offset|length|style|CODE|4162428|，因此Person可能是合适的属性名|4162429|entityMap^0|0|0|0|U|5|14|7|0|3|6|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|S|8|@$H|T|I|U|J|K]|$H|V|I|W|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@$H|Y|I|Z|J|K]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|O|$]]

I don't think there's a hard and fast rule, but generally I like to stick to the following guidelines as much as possible:

<ul>
<li>Don't repeat the name of the class. This one can be surprisingly hard to work around, but it's usually solved by thinking hard about the second rule:</li>
<li>Think about the properties role in the class, and not just what it is. In your example, <code>Owner</code> might be an appropriate property name, since a <code>Person</code> owns a particular <code>Address</code>.</li>
</ul>

blocks|key|1642564|text|选择一个并坚持下去。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1642565|在你的特定情况下，我想知道为什么一个人从属于一个地址，而不是反过来，但基本上就是选择一个你想使用的地址并继续使用它。只要它不是完全不可读的东西，或者不违反某种团队编码指南，你就很可能是好的。|1642566|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Pick one and stick with it.

In your specific case, I wonder why a person is subordinate to an Address, instead of the other way around, but basically just pick the one you want to use and keep using it. As long as it's not something completely unreadable or against some kind of Team coding guidelines, you're probably good.

If you a have Person Property on Address defined like

<pre><code>public class Address
{
 public int AdressId {get; set;}
 public Person AddressesPerson {get;set;}
 public string FullAddress {get; set;}
}
</code></pre>

What is the proper conventions, if any, for naming a property of another type?

Naming Conventions for Property Types

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如果您在Address上定义了Person属性，则public class Address{   public int AdressId {get; set;}   public Person AddressesPerson {get;set;}   public string FullAddress {get; se...

问属性类型的命名约定
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问属性类型的命名约定EN