You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Consider removing or breaking out http/request helpers #575
Is your feature request related to a problem? Please describe.
The module can't be used in across node/browser/react-native environments by default. Because the http module is only available in node you have to use the browser bundle which is awkward if you're including cloudevents within a npm package you're using across different environments. Similar issue reported here #534
Describe the solution you would like to see
Remove the request helpers or break them out into a separate package.
Additional context
It feels like the core library should focus on the cloudevent spec (creating & validating events) only and leave the implementation of sending events up to the developer. I do see the value in having something available out the box, but in our case we have existing implementations in place for http/websockets etc.
To work around this we have to conditional import the browser bundle which is a lot more awkward than just a simpler, universal package.
I'm facing the same issue.
I would like to only use the CloudEvent format, serialize it with the serializer I want, then send it whatever the protocol is (on our case, via WebSocket using Socket.io).
Ideal solution would be to have a "core" package that will only implement the CloudEvent format without any other OSS dependency.
I like the way the Cloudevents JAVA SDK provide different packages based on each need, so we can use the only necessary dependencies for our project and also limit security exposure area with too many sub dependencies that are not needed for our project. Even serializers should not be part from the core package.
Basically, on the JAVA SDK, you can choose to use different packages for each project requirements:
protocol (http, amqp, ...)
serializer (json, xml, ..)
available in pure java or via spring implementation
Activity
github-actions commentedon Jan 13, 2024
This issue is stale because it has been open 30 days with no activity.
YohanSciubukgian commentedon Mar 6, 2024
I'm facing the same issue.
I would like to only use the CloudEvent format, serialize it with the serializer I want, then send it whatever the protocol is (on our case, via WebSocket using Socket.io).
Ideal solution would be to have a "core" package that will only implement the CloudEvent format without any other OSS dependency.
I like the way the Cloudevents JAVA SDK provide different packages based on each need, so we can use the only necessary dependencies for our project and also limit security exposure area with too many sub dependencies that are not needed for our project. Even serializers should not be part from the core package.
Basically, on the JAVA SDK, you can choose to use different packages for each project requirements:
github-actions commentedon Apr 6, 2024
This issue is stale because it has been open 30 days with no activity.