Skip to content

v0.10.0 - Adding support for CloudEvents v1.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@n3wscott n3wscott released this 21 Oct 17:30
v0.10.0
2fa4bb1
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Changes to support 1.0

  • Added new types, types.URI and types.URIRef
  • Lots of work into converting extensions in and out of canonical string forms.
  • Deprecated DataContentEncoding, replaced with json property called data_base64.
    This is accessed by setting a []byte as data and using structured encoding.
  • All currently supported Transports (soon to be called Bindings) support 1.0.

Bug Fixes:

  • HTTP codec creation race condition has been fixed.
  • Time is parsed only in the type converters now.
  • Content-Type was assumed to always be Application/json. The sdk no longer
    defaults. If you find issues, try setting the DataContentType to application/json
  • DataContentType now supports text/plain.
  • Converter functions are now allowed to return nil, nil to mean nop/skip this
    payload, which results in a 204 status code for HTTP.

Prep for SDKv2:

  • AMQP binding has been rewritten in the internal details.
  • New packages now exist, pkg/binding and pkg/bindings exist as an attempt
    to rewrite the SDK to be a bit more event-like, the plan is to standardize
    some of the API and create Bindings (renamed from Transport) without assumed
    responses. We will have two kinds of Bindings, unidirectional, and
    bidirectional. More details to come as work continues.
Assets 2
Loading