Nick Chapsas

The preview version of v3 is out. The main thing I need to do is rewrite the unit tests and the integration tests. Once that's done it should be good...

Unfortunately I don't have the time anymore to work on this, mainly because I don't work with Cosmos anymore. If someone is willing to give the project a hand you...

I didn't quite get the question. Cosmonaut works with POCO entities as well and you can have mappings using attributes if the property name in the POCO is different from...

Yeah so you can use the [JsonProperty()] attribute to override the name.

This line: `var workflow = await _cosmosStore.FindAsync(command.WorkflowId, new PartitionKey("id"));` needs to be: `var workflow = await _cosmosStore.FindAsync(command.WorkflowId, new PartitionKey(command.WorkflowId));`

Hey @ThomasVandenbon, I can't quite remember why I removed it but I think when i was testing it, it wasn't working as it used to in v2 so I had...

What the? I can't understand how this could happen. Do you have the ApplicationInsights logging enabled? How can the exception happen but by be null? 😲 Can you reproduce this...

The thing is that you wouldn't see any exception because for this to be caused the Aggregate Exception was null. I am so confused.

This best practice must be new. It definately wasn't the recommendation before. I've personally seen scenarios where setting this to -1 can cause some serious performance issues.. I am willing...

Thanks for this @Mortana89. >When using the maxitemcount of -1, you'll get bigger RU spikes which could also cause performance issues if the RU spike is lower than the available...