Skip to content

ParseWebSocketSpeechResult incorrect #4

Description

@andymule

Great demo, thanks for sharing it!

Looks like they changed the format of the result, and since the parser relies on line numbering, it fails now. The quick fix is easy enough: Just swap case 1 and case 2. The better fix is to actually parse by content and not rely on line numbering nor character positioning.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions