Enable patching OData GeoSpatial properties in ODataV4TestService
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 111
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
Thursday Jan 29, 2015 at 01:46 GMT
Originally opened as https://github.com/Microsoft/vipr-old/issues/84
\vipr\test\ProxyExtensionsUnitTests\Given_An_EntityType_From_Server.cs
When_Updating_GeoSpatial_Primitive_Property_On_Client_Then_That_Property_Must_Be_Updated_On_Server
Using a GeoSpatial property seems to be causing issues with converting the payload into a Delta. This issue, deserialization of GeoJson, is discussed in a few places like http://blogs.microsoft.co.il/applisec/2014/06/03/spatial-support-in-web-api-and-odata/. Unfortunately, it seems that since we are using Delta a custom Json deserializer is not even getting triggered. We need to find a workaround for this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in vipr/test/ProxyExtensionsUnitTests/Given_An_EntityType_From_Server.cs and run When_Updating_GeoSpatial_Primitive_Property_On_Client_Then_That_Property_Must_Be_Updated_On_Server. Trace how the GeoSpatial payload is converted into Delta and why GeoJson deserialization is not reached. Done means the GeoSpatial property can be patched on the client and is updated on the ODataV4TestService server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100