-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CloudEvent constructor should accept inline extensions #209
Comments
@lance should the extensions property in your example, be an array of key:value pairs? |
The reason I ask is because if you take a look at what is created after doing The extensions property is a blank array
As soon as you call
Not sure what the correct answer should be here |
@lholmquist that was a bug that was fixed at the end of last week https://github.com/cloudevents/sdk-javascript/pull/202/files#diff-695048fccf8efadd88b77db776a94d06L84. It should be an object. |
@lance yea, i was just looking in the code and couldn't find that array, and just realized my example was using the version on npm. 🤦 |
* This allows someone to pass an extension/extensions into the CloudEvent contructor when creating a CloudEvent. fixes cloudevents#209 Signed-off-by: Lucas Holmquist <lholmqui@redhat.com>
* This allows someone to pass an extension/extensions into the CloudEvent contructor when creating a CloudEvent. fixes cloudevents#209 Signed-off-by: Lucas Holmquist <lholmqui@redhat.com>
* This allows someone to pass an extension/extensions into the CloudEvent contructor when creating a CloudEvent. fixes cloudevents#209 Signed-off-by: Lucas Holmquist <lholmqui@redhat.com>
* feat!: pass extension into the constructor. * This allows someone to pass an extension/extensions into the CloudEvent contructor when creating a CloudEvent. fixes #209 Signed-off-by: Lucas Holmquist <lholmqui@redhat.com>
There is no way to create a
CloudEvent
instance using the constructor and have the extensions initialized there. For example, this is not valid, but should work.The text was updated successfully, but these errors were encountered: