Skip to content

Commit f9d8f70

Browse files
Update coreTypes.md
Add link to nav prop article
1 parent 5d907fc commit f9d8f70

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

graph/articles/coreTypes.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,7 @@ The following types are identified as core types, and will require strong justif
1717
## Alternatives to Adding Structural Properties
1818

1919
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 new type on the existing type.
23-
- Contain the new type in an entity set elsewhere, and add a navigation property to the existing type on the new type.
20+
Then, model the relationship between the existing core type and the new type by adding a navigation property. For information on modeling with navigation properties, see [Navigation Property](../patterns/navigation-property.md).
2421

2522
## Example:
2623

@@ -39,7 +36,7 @@ Don't add new properties to core types such as `user`.
3936

4037
### Do:
4138

42-
Do one of the following:
39+
Model the information by creating a new type and model the relationship to the existing core type with a navigation property. To determine which option is most appropriate, see [Navigation Property](../patterns/navigation-property.md):
4340

4441
#### Option 1: Add a navigation property on the existing type to the new type, containing the new type.
4542

0 commit comments

Comments
 (0)