cloudevents / cloudevents/sdk-java
Why do sometimes headers start with "ce-" and sometimes with "ce_"?
Open
Nobody has claimed this yet.
question
- Dominant language
- Java
- Stars
- 446
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
Why is there such a difference?
- For example in the docs for kafka it is an underscore: https://github.com/cloudevents/spec/blob/v1.0.1/kafka-protocol-binding.md#325-example
- At the same time it is a dash in the Spring module in this project.
It makes it so complicated to use cloudevents-spring together with cloudevents-kafka. Why is there such inconsistency?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the Kafka protocol binding example linked in the issue with the header handling in the Spring module. Determine whether the ce_ versus ce- difference is intentional or inconsistent, then align the affected behavior or documentation and verify that CloudEvents can be used consistently across the Kafka and Spring integrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100