Skip to content

bug in ws client for streamed readings #38

Description

@edaniszewski

the data that is marshalled into a Reading is incorrect, as done via the websocket streamed readings. instead of initializing with the reading data, it initializes with the whole websocket payload which includes the metadata frame which wraps the reading.

this is a pretty straightforward fix. instead of passing in the entire websocket response, just pass in the synse data embedded within the ws response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood first issueGood for newcomers

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions