6.0.5

[adrianhall]

What's Changed

• (#795) Allow specification of the contract resolver. by @adrianhall in (#795) Allow specification of the contract resolver. #796
• (#797) expand table operation errors to all JSON errors. by @adrianhall in (#797) expand table operation errors to all JSON errors. #798
• (#799) IEdmModel Options updates by @adrianhall in (#799) IEdmModel Options updates #801
• (#805) Fixes / skips for non-working tests. by @adrianhall in (#805) Fixes / skips for non-working tests. #806
• Basic test for ContractResolver by @fileman in Basic test for ContractResolver #803
• (#808) Added SendAsync support for the internal HttpClient. by @adrianhall in (#808) Added SendAsync support for the internal HttpClient. #810
• (#809) Remove error entries on a successful push. by @adrianhall in (#809) Remove error entries on a successful push. #811
• (#809) LoadErrorsAsync updated to load errors for a list of tables. by @adrianhall in (#809) LoadErrorsAsync updated to load errors for a list of tables. #812

Full Changelog: 6.0.4...6.0.5

---

This discussion was created from the release 6.0.5.

[adrianhall]

Hey folks,

Back with a bumper release today.

On the server side, you can now either specify an IEdmModel that you built, or we will cache the ones we build. This is for memory efficiency. Thanks to @mpopowicz for the report.

On the client side, I've updated the conflict resolution error handling (thanks to @Arslan007 for the detailed issue). The errors table used to be loaded en-masse when reporting errors. Now, only the errors for tables that are in focus for the push are loaded. In addition, @amertlich reported an error when clearing errors from the operations queue, and that was fixed too.

Finally, also on the client side, you can use the same pipeline that the DatasyncClient uses for sending "random HTTP commands" to the server, by called var response = await client.SendAsync(request); - client is the DatasyncClient, and it acts in the same way as SendAsync() for the HttpClient (in fact, it is just passed through). It does authentication and anything else in the pipeline you've configured.

As always, happy to take issues - please file one issue for each problem you are experiencing. Don't combine them - the extra ones get lost.