Skip to content

How to handle beta vs non-beta streaming shapes without duplicating code? #257

@akosyakov

Description

@akosyakov

I'm using both standard features and beta features in my Go app. The streaming event shapes are completely different between non-beta and beta streaming, which means I need to implement streaming logic twice. Is it safe to just use beta streaming for everything (even without beta headers)? Or what's the recommended pattern to avoid maintaining two separate implementations? How are others handling this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions