You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/api/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ What happens after your client disconnects is dependent on whether the session h
22
22
* If resuming is disabled all voice connections are closed immediately.
23
23
* If resuming is enabled all music will continue playing. You will then be able to resume your session, allowing you to control the players again.
24
24
25
-
To enable resuming, you must call the [Update Session](#update-session) endpoint with the `resuming` and `timeout`.
25
+
To enable resuming, you must call the [Update Session](../api/rest.md#update-session) endpoint with the `resuming` and `timeout`.
26
26
27
27
To resume a session, specify the session id in your WebSocket handshake request headers:
28
28
@@ -36,7 +36,7 @@ You can tell if your session was resumed by looking at the handshake response he
36
36
Session-Resumed: true
37
37
```
38
38
39
-
In case your websocket library doesn't support reading headers you can listen for the [ready op](#ready-op) and check the `resumed` field.
39
+
In case your websocket library doesn't support reading headers you can listen for the [ready op](../api/websocket.md#ready-op) and check the `resumed` field.
40
40
41
41
When a session is paused, any events that would normally have been sent are queued up. When the session is resumed, this
42
42
queue is then emptied and the events are replayed.
Copy file name to clipboardExpand all lines: docs/changelog/index.md
+25-25Lines changed: 25 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,24 +17,24 @@ The most noteworthy of these, as well as any features and breaking changes, are
17
17
*`v4` uses the `sessionId` instead of the `resumeKey` for resuming.
18
18
*`v4` now returns the tracks `artworkUrl` and `isrc` if the source supports it.
19
19
* removal of deprecated json fields like `track`.
20
-
* addition of `artworkUrl` and `isrc` fields to the [Track Info](#track-info) object.
21
-
* addition of the full [Track](#track) object in [TrackStartEvent](#trackstartevent), [TrackEndEvent](#trackendevent), [TrackExceptionEvent](#trackexceptionevent) and [TrackStuckEvent](#trackstuckevent).
22
-
* updated capitalization of [Track End Reason](#track-end-reason) and [Severity](#severity)
* addition of `artworkUrl` and `isrc` fields to the [Track Info](../api/rest.md#track-info) object.
21
+
* addition of the full [Track](../api/rest.md#track) object in [TrackStartEvent](../api/websocket.md#trackstartevent), [TrackEndEvent](../api/websocket.md#trackendevent), [TrackExceptionEvent](../api/websocket.md#trackexceptionevent) and [TrackStuckEvent](../api/websocket.md#trackstuckevent).
22
+
* updated capitalization of [Track End Reason](../api/websocket.md#track-end-reason) and [Severity](../api/websocket.md#severity)
@@ -72,7 +72,7 @@ All websocket ops are deprecated as of `v3.7.0` and replaced with the following
72
72
73
73
* Added filters
74
74
* The `error` string on the `TrackExceptionEvent` has been deprecated and replaced by
75
-
the [Exception](#exception-object) object following the same structure as the `LOAD_FAILED` error on [`/loadtracks`](#track-loading).
75
+
the [Exception](../api/websocket.md#exception-object) object following the same structure as the `LOAD_FAILED` error on [`/loadtracks`](../api/rest.md#track-loading).
76
76
* Added the `connected` boolean to player updates.
77
77
* Added source name to REST api track objects
78
78
* Clients are now requested to make their name known during handshake
0 commit comments