Lance Ball

In the JavaScript SDK, the behavior is essentially the same as in Ruby. We do not validate non-spec extensions, and the type can be anything, but in practice it's typically...

Closing as obsolete

> `HTTP.toEvent` should throw to prevent this. I don't think it should, to be honest. This is similar to other scenarios that have been pointed out with regard to receiving...

> event should have subject: '' and event.validate() should throw. Hmm, since `subject` is an optional attribute, it seems odd to throw if it's empty - even if the spec...

@lholmquist I started to look into this, and it's not clear what the best way to determine the next version should be. The release-please library and action don't expose a...

@FelixHarvey @evanshortiss thank you for your detailed descriptions of the issues you are seeing with the SDK - and I would welcome any contributions you have towards improvement. The interfaces...

@cardil you are correct to point out the error in my example. But your example would not produce a valid CE even if we could handle big integers, because the...

Closing and reopening to trigger re-run of CI with updated package.json (to hopefully fix errors)

@cardil good catch! > A Distributed Tracing Extension is part of [the specification](https://github.com/cloudevents/spec/blob/master/extensions/distributed-tracing.md). Javascript SDK should support it. To be clear, expectations for the SDKs do not require that this...

@cardil I've been thinking about this, and I wonder how you see this in practical usage. In the [spec](https://github.com/cloudevents/spec/blob/master/extensions/distributed-tracing.md#using-the-distributed-tracing-extension), the example given is, ``` CURL -X POST example/webhook.json \ -H...