* CloudEvents v0.2 support, step 1: interfaces and versioned types.
Signed-off-by: Evan Anderson <evan.k.anderson@gmail.com>
* Add support for v0.2 event types. (Breaking change in return types!)
Signed-off-by: Evan Anderson <evan.k.anderson@gmail.com>
* Move DataContentType() to be common across Senders and Receivers.
Signed-off-by: Evan Anderson <evan.k.anderson@gmail.com>
* Add comment on why test code is commented out.
Signed-off-by: Evan Anderson <evan.k.anderson@gmail.com>
* Address @vagababov review.
* Add another test case and better cover extensions in handler tests.
* Some fixes to the event_v01.go file.
Mostly change to the encodeKey to not use pointer to the map.
Some minor readability improvements.
* Fix the comment wording.
* Add docs to help bootstrap cloud event sdk usage.
* add go markdown label.
* prettier markdown.
* well golang wants tabs but markdown does not i guess so... fight!
* adding me as an owner of this code.
* adding ville to the hook.
* Pushing new client and builder.
* good example of how to use the encoding settings int he builder.
* make it more clear,.
* prep for merge.
* adding tests.
* adding extenion tests.
* adding test for empty original extensions.
* Adding valid builder tests.
* adding client tests.
* Removing encoding from enum names.
* ran prettier.
* fix spacing.
* Update cloudevents/README.md
Co-Authored-By: n3wscott <32305648+n3wscott@users.noreply.github.com>
* Update based on feedback.
* adding builder to new client.
* update producer paragraph.
* trail space.
* trail space.
* Some fixes to the spoof.go and exporter.go
While reviewing some other CL, I saw some avenues for improving
spoof.go, to log the URL that's being fetched, which would help in test
debugging and to use switch construct, rather than nested if's.
While testing the change, I noticed some shifty loggin from the
exporter, so I fixed that as well while I was there.
* Continuation of the previous cleanups.
* Fix the issues with formatting by executing a grep
* and fix compilation error
* lowercase error
* fix the newly changed unit test