teutat3s/elk
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

fix: initialise stream promise before stream is available (#1191)

Browse source
This commit is contained in:
Daniel Roe 2023-01-15 20:26:59 +00:00 committed by GitHub
parent a594f6f167
commit cd8e2cb6a4
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
composables/masto/notification.ts
View file

@ -12,20 +12,24 @@ export const useNotifications = () => {
return
const lastReadId = notifications[id]![1][0]
notifications[id]![1] = []
await client.v1.markers.create({
notifications: { lastReadId },
})
if (lastReadId) {
await client.v1.markers.create({
notifications: { lastReadId },
})
}
}
async function connect(): Promise<void> {
if (!isHydrated.value || !id || notifications[id] || !currentUser.value?.token)
return
let resolveStream
const stream = new Promise<WsEvents>(resolve => resolveStream = resolve)
notifications[id] = [stream, []]
await until($$(canStreaming)).toBe(true)
const stream = client.v1.stream.streamUser()
notifications[id] = [stream, []]
client.v1.stream.streamUser().then(resolveStream)
stream.then(s => s.on('notification', (n) => {
if (notifications[id])
notifications[id]![1].unshift(n.id)