operator-framework / operator-framework/java-operator-sdk
InformerEventSource public API refinements
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 944
- Forks
- 242
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 43
Description
Currently InformerEventSource and ControllerEventSource extends ManagedEventSource; but this results in methods which are public but otherwise just should be hidden from the users.
We should refine this, and just exposes methods which are user facing as public; In other words we should have composition over inheritance.
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 examining InformerEventSource, ControllerEventSource, and ManagedEventSource to inventory the inherited public methods and distinguish user-facing behavior from implementation details. Confirm the intended public surface and composition design with the project’s API conventions; the work is done when only user-facing methods remain publicly exposed without the unwanted inherited API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100