Skip to content

tech-debt(audio): API naming consistency + deprecation plan #10

Description

@morozsm

Why

Audio APIs now mix low-level and high-level concepts; naming should be consistent and migration predictable.

Scope

  • Define canonical naming for low-level vs high-level audio methods
  • Add deprecation warnings where needed
  • Publish migration notes

Acceptance Criteria

  • Clear naming map documented
  • Deprecation warnings in place
  • Backward compatibility preserved through deprecation window

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:audioAudio subsystem, codec, streamspriority:P2Lower prioritytype:tech-debtInternal cleanup/refactor/deprecation

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions