-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Initialize project (again) #2
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
Conversation
Remove row-types refactor: Slightly update some imports build: Update extra-deps in stack lts yamls Remove unsupported lts yamls style: Format CE JSON spec build: Fix Kafka client import docs: Flesh out readme some more feat: Simplify implementation, remove row-types
mjgpy3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Really nice documentation throughout.
I could see us eventually splitting out different bindings into different packages (similarly how you'll see persistent for engine-agnostic stuff and persistent-postgresql for postgres-specific stuff).
|
@mjgpy3 that makes sense, I kinda just followed the structure in the JS SDK but I don't see why we couldn't split this out as you say |
|
@OlaoluwaM yeah and it's really not necessary to split at the moment. |
Unofficial Haskell SDK for the cloudevents spec. Written with row types to allow for arbitrary extension attributes as per the spec requirements. This time without row-types.
This is a bare bones SDK that only allows for:
Currently only missing field deduplication