Skip to content

[0.4.3] - 2024-10-19
Compare
Choose a tag to compare
@berezovskyi berezovskyi released this 19 Oct 17:06
· 64 commits to main since this release
v0.4.3
18b9609
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Security

This release does not contain security updates.

Added

  • ️⚡️ An example project using OslcClient and basic auth to retrieve a WorkItem (OSLC ChangeRequest) from Jazz.
  • OslcClient::ForBasicAuth() factory method.
  • ️️️⚡️ OslcClient.GetResourceAsync() strongly typed async method that returns OslcResponse<T> with either a typed resource or an error.
  • Support for complex MIME type strings for content negotiation. Current Accept string is set to text/turtle;q=1.0, application/rdf+xml;q=0.9, application/n-triples;q=0.8, text/n3;q=0.7 by default.
  • OSLC Query results now expose a .TotalCount property.

Changed

  • ❗️ OSLC4Net.Client now requires netstandard2.1 (was: netstandard2.0). No longer usable under .NET Framework 4.x.
  • Upgraded dotNetRDF to v3.3.0

Deprecated

  • Some constructors on OslcClient were deprecated (around skipping TLS checks).
  • 👉 log4net logging will be replaced with the standard Microsoft ILogger in a future release.
  • Direct use of IEnumerator properties on OslcQueryResponse to iterate over response pages.
  • Multiple symbols on OSLC Query related code with Java-like signatures (various Get* methods) and string types. Prefer C# props of type Uri.

Removed

This release does not remove any features.

Fixed

  • OslcClient no longer overwrites most of the headers (#204). It was a similar issue to #19 (but happening with OslcRestClient).
  • Ensure OSLC Query responses are processed correctly when they contain multiple oslc:ResponseInfo objects (!203).

The release build looks like it has failed, but the release was successful - an examples project failed to publish, which is actually good.

Assets 2
Loading