You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 12, 2020. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -131,12 +131,10 @@ The `CosmosEntityName` will be used to make the object identifiable for Cosmosna
131
131
132
132
Once you set this up you can add individual CosmosStores with shared collections.
133
133
134
-
Something worths noting is that because you will use this to share objects partitioning will be virtually impossible. For that reason the `id` will be used as a partition key by default as it is the only property that will be definately shared between all objects.
135
-
136
134
### Restrictions
137
135
Because of the way the internal `id` property of Cosmosdb works, there is a mandatory restriction made.
138
136
You cannot have a property named Id or a property with the attribute `[JsonProperty("id")]` without it being a string.
139
-
A cosmos id need to exist somehow on your entity model. For that reason if it isn't part of your entity you can just extend the `CosmosEntity` class.
137
+
A cosmos id needs to exist somehow on your entity model. For that reason if it isn't part of your entity you can just extend the `CosmosEntity` class.
140
138
141
139
It is **HIGHLY RECOMMENDED** that you decorate your Id property with the `[JsonProperty("id")]` attribute to prevent any unexpected behaviour.
142
140
@@ -241,5 +239,3 @@ If you already have initialised `TelemetryConfiguration` for your application th
0 commit comments