Skip to content
This repository was archived by the owner on Jul 12, 2020. It is now read-only.

Commit 92b5da0

Browse files
authored
Update README.md
1 parent 61bbd0d commit 92b5da0

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

README.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -131,12 +131,10 @@ The `CosmosEntityName` will be used to make the object identifiable for Cosmosna
131131

132132
Once you set this up you can add individual CosmosStores with shared collections.
133133

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-
136134
### Restrictions
137135
Because of the way the internal `id` property of Cosmosdb works, there is a mandatory restriction made.
138136
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.
140138

141139
It is **HIGHLY RECOMMENDED** that you decorate your Id property with the `[JsonProperty("id")]` attribute to prevent any unexpected behaviour.
142140

@@ -241,5 +239,3 @@ If you already have initialised `TelemetryConfiguration` for your application th
241239
| UpdateRangeAsync |1129ms|
242240
| UpsertRangeAsync |1034ms|
243241
| RemoveRangeAsync | 899ms |
244-
245-

0 commit comments

Comments
 (0)