Skip to content

Commit 5818436

Browse files
Update coreTypes.md
1 parent 57e6d71 commit 5818436

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

graph/articles/coreTypes.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -16,12 +16,11 @@ The following types are identified as core types, and will require strong justif
1616

1717
## Alternatives to Adding Structural Properties
1818

19-
Instead of adding a structural property to an existing type, do the following:
20-
1. Create a new type that models the information captured in the proposed structural property.
21-
2. Create a navigation property linking the new type to the existing type, doing one of the following:
22-
- Contain the new type in an entity set elsewhere, and add a navigation property to the existing type on the new type.
23-
- Contain the new type in an entity set elsewhere, and add a navigation property to the new type on the existing type.
24-
- Add a navigation property to the new type on the existing type, containing the new type.
19+
Instead of adding a structural property to the existing type (`user`, `group` or `device`), create a new type that models the information captured in the proposed structural property(s).
20+
Then, do one of the following:
21+
- Add a navigation property on the existing type to the new type, containing the new type.
22+
- Contain the new type in an entity set elsewhere, and add a navigation property to the existing type on the new type.
23+
- Contain the new type in an entity set elsewhere, and add a navigation property to the new type on the existing type.
2524

2625
## Example:
2726

@@ -40,16 +39,18 @@ Don't add new properties to core types such as `user`.
4039

4140
### Do:
4241

43-
Instead, create a new entity modeling the concept that you wish to introduce, and create a navigation property connecting that entity to the desired type.
42+
First, create a new type that models the information captured in the desired structural property(s).
4443

4544
```xml
4645
<EntityType name="bankAccountInformation">
4746
<Property Name="accountNumber" Type="Edm.string"/>
4847
<Property Name="routingNumber" Type="Edm.string"/>
4948
</EntityType>
49+
```
5050

51-
...
51+
Then, for example, add a navigation property on the existing type, containing the new type:
5252

53+
```xml
5354
<EntityType name="user">
5455
<NavigationProperty Name="bankAccountInformation" Type="bankAccountInformation" ContainsTarget="true"/>
5556
</EntityType>

0 commit comments

Comments
 (0)