cloudevents / cloudevents/sdk-java
Enhancement: generalise the validation in wrapper library
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 446
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
Adding a validation wrapper Library separated from manifests. By adding this in our library we are avoiding each validation to be added by each consumer.
cloudevents/spec#2 aspects:
- validation - IN-SCOPE
- governance - OUT-OF-SCOPE
sdk-java issue reference#: https://github.com/cloudevents/sdk-java/issues/592
slack Thread : https://cloud-native.slack.com/archives/C9DB5ABAA/p1696404658583879?thread_ts=1695874684.630259&cid=C9DB5ABAA
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 reviewing the wrapper library and manifest-related validation context in sdk-java, then read the linked sdk-java issue #592 and the referenced CloudEvents discussion. Done means defining and implementing a shared validation wrapper separated from manifests; governance is explicitly out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100