Skip to content

Use consistent naming convention for component parser retrieval functions #4492

@Horiodino

Description

@Horiodino

Component(s)

No response

Describe the issue you're reporting

Description

Currently, in apis/v1beta1/config.go, the code uses inconsistent function names (ReceiverFor, ParserFor, etc.) when retrieving component parsers. These functions serve the same purpose but have different names across component kinds (receivers, exporters, processors, and extensions), leading to confusion and inconsistency in the codebase.

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions