Centralize Avro converter handling [DBZ-2260]
Open
component/core-library
migrated-from-jira
type/task
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-2260](https://issues.redhat.com/browse/DBZ-2260)
We now support two Avro converters. The usage of Avro is spread across the code base - like {{CommonConnectorConfig}}, cloud events, tests etc.
We should extract all the related logic and centralize it in a single utility class.
Contributor guide
Research direction
Start by locating the Avro-related logic currently spread through CommonConnectorConfig, cloud events, and tests. Trace how the two supported converters are handled and identify the shared behavior for a utility class; the work is done when those callers use the centralized logic and the affected tests pass.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100