Would it be possible to add [DataContract] to the spatial classes about azure-cosmos-dotnet-v3

[ealsur]

@jackbond Is this a blocker in your current project? We have this in the roadmap but if you are blocked we can take that into account to prioritize.

[jackbond]

Well I could say it was a blocker, but at this point it's really just an inconvenience. The reality is, the Service Fabric guys have provided a means to write custom serializers for their actor and service calls, but it's full of gotchyas. For example, we wrote one so that we could pass our objects that have a property of DocumentDb.Spatial.Point, but then that messed up the serialization of Exceptions (which I haven't had the time to figure out if there is a workaround.)

Fundamentally, I don't know how much work it would take for you guys to support DataContract, but it does seem that two core Azure services should play a little nicer together. :)

[ealsur]

I agree. We'll keep it in the roadmap for GA to support this scenario :)

[operationslazlo326]

Is there an estimate for GA? There doesn't appear to be a whole lot of activity in regards to the source.

[j82w]

The current estimate for GA is the first half of 2019. This may change base on new feature requests.

[jackbond]

So I take it you guys aren't using this repository for your actual source control. It would be nice to be able to provide direct feedback based on ongoing code changes.

[jackbond]

Are you guys planning another preview? The lack of spatial support in the existing preview makes it rather difficult to experiment with. Thanks.

[j82w]

Hi @jackbond ,

We are planning do to another release soon. After that release we will move to using this repository as the actual source control.