Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expect to-device event list, not wrapper #287

Merged
merged 1 commit into from
Dec 19, 2022
Merged

Expect to-device event list, not wrapper #287

merged 1 commit into from
Dec 19, 2022

Conversation

AndrewFerr
Copy link
Contributor

Decrypted device events are now received as an array, not an object containing a array as a property.

Signed-off-by: Andrew Ferrazzutti [email protected]

Checklist

  • Tests written for all new code
  • Linter has been satisfied
  • Sign-off given on the changes (see CONTRIBUTING.md)

This is a follow-up of a4d9b03.

Decrypted device events are now received as an array, not an object
containing a array as a property.

Signed-off-by: Andrew Ferrazzutti <[email protected]>
@turt2live turt2live self-requested a review December 19, 2022 16:18
@turt2live turt2live merged commit 0474d68 into turt2live:main Dec 19, 2022
@AndrewFerr AndrewFerr deleted the af/to-device-array branch December 19, 2022 19:26
AndrewFerr added a commit to element-hq/matrix-bot-sdk that referenced this pull request Jul 19, 2023
OlmMachine.receiveSyncChanges returns an array of [device messages,
room key changes], so emit "to_device.decrypted" with that instead of
the entire array.

Fixes regression introduced by turt2live#287.
AndrewFerr added a commit to element-hq/matrix-bot-sdk that referenced this pull request Aug 2, 2023
OlmMachine.receiveSyncChanges returns an array of [device messages,
room key changes], so emit "to_device.decrypted" with that instead of
the entire array.

Fixes regression introduced by turt2live#287.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants