Skip to content

Commit e5f7c7d

Browse files
MattiasBuelensMattiasBuelens
authored
Fix Prettier (#166)
1 parent d761aa3 commit e5f7c7d

File tree

567 files changed

+7463
-8340
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

567 files changed

+7463
-8340
lines changed

‎.prettierignore

+6
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,12 @@
1111
.docusaurus
1212
.cache-loader
1313
static/theoplayer-license.txt
14+
theoplayer/changelog.md
15+
theoplayer/static/theoplayer/*/api-reference
16+
theoplayer_versioned_docs/*/changelog.md
17+
theoplayer_versioned_docs/*/static/theoplayer/*/api-reference
18+
theoads/api/ads-client.swagger.json
19+
theoads/api/signaling/
1420

1521
# Submodules
1622
theoplayer/external/

‎theoads/getting-started/00-getting-started-signaling-service.mdx

+5-4
Original file line numberDiff line numberDiff line change
@@ -33,10 +33,11 @@ For HLS, this means the `EXT-X-PROGRAM-DATE-TIME` tag must be present.
3333
Breaks can be scheduled using either the provided REST API or in the manifest itself.
3434

3535
#### Manifest
36+
3637
When using manifest triggers, the following tags are supported:
3738

3839
- `#EXT-X-DATERANGE` tag
39-
- this is recommended because of its standardization and ability to provide more comprehensive data for improved integration.
40+
- this is recommended because of its standardization and ability to provide more comprehensive data for improved integration.
4041
- `#EXT-X-OATCLS-SCTE35` tag
4142
- `#EXT-X-CUE-OUT` and `#EXT-X-CUE-OUT-CONT` tags
4243
- To use the tune-in feature, `#EXT-X-CUE-OUT-CONT` tags must be present between `#EXT-X-CUE-OUT` and `#EXT-X-CUE-IN` markers.
@@ -77,7 +78,7 @@ When setting up the Signaling Service, a configuration needs to be passed along.
7778
When playing a THEOads source, it is expected to pass a source that looks like this:
7879

7980
```js
80-
src: 'PATH-TO-SIGNALING-SERVER/hls/MANIFEST-URI'
81+
src: 'PATH-TO-SIGNALING-SERVER/hls/MANIFEST-URI';
8182
```
8283

8384
For the `MANIFEST-URI` part of the `src`, it can be an absolute URL or a relative one where the `origin` is not part of it.
@@ -86,10 +87,10 @@ Below shows an example for both cases:
8687

8788
```js
8889
// Absolute URL
89-
src: 'PATH-TO-SIGNALING-SERVER/hls/https://domain.com/manifest.m3u8'
90+
src: 'PATH-TO-SIGNALING-SERVER/hls/https://domain.com/manifest.m3u8';
9091

9192
// Relative URL
92-
src: 'PATH-TO-SIGNALING-SERVER/hls/manifest.m3u8'
93+
src: 'PATH-TO-SIGNALING-SERVER/hls/manifest.m3u8';
9394
```
9495

9596
In the case of the absolute URL the Signaling Service uses the whole URL as is. For the relative URL on the other hand,

‎theoads/getting-started/00-getting-started-web.mdx

+5-4
Original file line numberDiff line numberDiff line change
@@ -37,13 +37,14 @@ Since THEOads integrates with Google DAI Pod Serving, it is required to load the
3737
### Player configuration
3838

3939
To make use of the THEOads integration, first enable the feature in your player configuration:
40+
4041
```javascript
4142
const player = new THEOplayer.Player(element, {
4243
libraryLocation: 'YOUR-LIBRARY-LOCATION',
4344
license: 'YOUR-LICENSE-WITH-THEOADS',
4445
ads: {
45-
theoads: true
46-
}
46+
theoads: true,
47+
},
4748
});
4849
```
4950

@@ -86,8 +87,8 @@ You can pass your THEOads-enabled source directly to the UI's `source` property:
8687
libraryLocation: 'YOUR-LIBRARY-LOCATION',
8788
license: 'YOUR-LICENSE-WITH-THEOADS',
8889
ads: {
89-
theoads: true
90-
}
90+
theoads: true,
91+
},
9192
};
9293
ui.source = {
9394
sources: {

‎theoads/how-to-guides/create-backdrop-layout.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ sidebar_position: 6
33
---
44

55
# Create backdrop images
6+
67
A backdrop is an image that is shown along with the player during an ad.
78
This image is intended to provide some additional information about an advertisement.
89

@@ -25,7 +26,7 @@ Below is a template for the Double Box layout tailored for 1080p resolution:
2526

2627
### 2. L-Shape Layout
2728

28-
The **L-Shape** layout positions the video player in the top-left corner of the screen, scaling it down to create space for the backdrop image.
29+
The **L-Shape** layout positions the video player in the top-left corner of the screen, scaling it down to create space for the backdrop image.
2930
This configuration allows viewers to see the ad and the backdrop image simultaneously.
3031

3132
- **Screen Ratio:** 16:9, ensuring compatibility with most screens.

‎theoplayer/api-reference/roku.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ The following key/value pairs are supported on the `drmParams` attribute of a Co
107107
## Methods
108108

109109
| Method | Description |
110-
|---------------------------------------------------------------------------------| ------------------------------------------------------------------------------------------------------------------------------------------------------ |
110+
| ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
111111
| addEventListener | |
112112
| destroy | Destroy the player. |
113113
| pause | Pause playback. |

‎theoplayer/examples/shared.module.css

+6-6
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
.player {
2-
width: 100%;
3-
/*
4-
* Make the player slightly higher than necessary,
5-
* to avoid scrollbars.
6-
*/
7-
aspect-ratio: 16 / 9.1;
2+
width: 100%;
3+
/*
4+
* Make the player slightly higher than necessary,
5+
* to avoid scrollbars.
6+
*/
7+
aspect-ratio: 16 / 9.1;
88
}

‎theoplayer/faq/02-how-to-combat-autoplay-policies.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ THEOplayer has the `mutedAutoplay` property in the `PlayerConfiguration`. When y
2727
// ...
2828
var player = new THEOplayer.Player(element, {
2929
// ...
30-
mutedAutoplay: "all"
30+
mutedAutoplay: 'all',
3131
// ...
3232
});
3333
// ...

‎theoplayer/faq/15-which-error-related-events-does-player-expose.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Note that only the `error` events in the "Player API" are fatal.
77
Error events dispatched in different APIs (e.g. Ads API) are considered non-fatal, because some level of playback might still be possible, or the video player might recover from it.
88

99
| API | Event | Use | Example/how to trigger |
10-
| :--------------------: | :------------------------------------------: | :----------------------------------------------------------------------------: |:-------------------------------------------------------------------------------:|
10+
| :--------------------: | :------------------------------------------: | :----------------------------------------------------------------------------: | :-----------------------------------------------------------------------------: |
1111
| Player | error | Triggered for media issues, NOT network issues | A poorly encoded segment |
1212
| | segmentnotfound (not on iOS + only for DASH) | A segment was not found | A 404 returned on a segment |
1313
| Ads API | aderror | Something went wrong during ad handling | Empty ad tag / Adblocker |

‎theoplayer/faq/16-why-did-subtitles-stop-working.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ This question is occasionally asked by developers who've configured the latest r
77
The most common reason on an older build why closed captions are no longer working is because the **`texttrackrendering` feature isn't enabled**. To verify whether this feature is enabled you can execute the query below.
88

99
```js
10-
var subsEnabled = THEOplayer.features.indexOf("texttrackrendering") > -1;
10+
var subsEnabled = THEOplayer.features.indexOf('texttrackrendering') > -1;
1111
```
1212

1313
### After version 2.80

‎theoplayer/faq/21-why-does-currentime-seem-to-be-off.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,9 @@ function AbsoluteTimeline(player) {
3939

4040
function durationchangeHandler() {
4141
timeOffset = player.seekable.start(0);
42-
player.removeEventListener("durationchange", durationchangeHandler);
42+
player.removeEventListener('durationchange', durationchangeHandler);
4343
}
44-
player.addEventListener("durationchange", durationchangeHandler);
44+
player.addEventListener('durationchange', durationchangeHandler);
4545

4646
return {
4747
getOffset: function () {
@@ -52,7 +52,7 @@ function AbsoluteTimeline(player) {
5252
},
5353
seek: function (timestamp) {
5454
player.currentTime = timestamp + timeOffset;
55-
}
55+
},
5656
};
5757
}
5858

‎theoplayer/faq/36-can-clipping-be-used-in-a-playlist.md

+23-24
Original file line numberDiff line numberDiff line change
@@ -21,40 +21,39 @@ var playlist = [
2121
{
2222
source: {
2323
sources: {
24-
src: "https://cdn.theoplayer.com/video/big_buck_bunny/big_buck_bunny_metadata.m3u8",
24+
src: 'https://cdn.theoplayer.com/video/big_buck_bunny/big_buck_bunny_metadata.m3u8',
2525
startTime: 100,
26-
endTime: 150
26+
endTime: 150,
2727
},
28-
title: "Big Buck Bunny",
29-
description: "Big Buck Bunny",
30-
poster: "https://cdn.theoplayer.com/video/big_buck_bunny/poster.jpg"
31-
}
28+
title: 'Big Buck Bunny',
29+
description: 'Big Buck Bunny',
30+
poster: 'https://cdn.theoplayer.com/video/big_buck_bunny/poster.jpg',
31+
},
3232
},
3333
{
3434
source: {
3535
sources: {
36-
src: "https://cdn.theoplayer.com/video/star_wars_episode_vii-the_force_awakens_official_comic-con_2015_reel_(2015)/index.m3u8",
36+
src: 'https://cdn.theoplayer.com/video/star_wars_episode_vii-the_force_awakens_official_comic-con_2015_reel_(2015)/index.m3u8',
3737
startTime: 120,
38-
endTime: 180
38+
endTime: 180,
3939
},
40-
title: "Star Wars Reel",
41-
description: "Star Wars Reel",
42-
poster:
43-
"https://cdn.theoplayer.com/video/star_wars_episode_vii-the_force_awakens_official_comic-con_2015_reel_(2015)/poster.jpg"
44-
}
40+
title: 'Star Wars Reel',
41+
description: 'Star Wars Reel',
42+
poster: 'https://cdn.theoplayer.com/video/star_wars_episode_vii-the_force_awakens_official_comic-con_2015_reel_(2015)/poster.jpg',
43+
},
4544
},
4645
{
4746
source: {
4847
sources: {
49-
src: "https://cdn.theoplayer.com/video/tears_of_steel/index.m3u8",
48+
src: 'https://cdn.theoplayer.com/video/tears_of_steel/index.m3u8',
5049
startTime: 50,
51-
endTime: 150
50+
endTime: 150,
5251
},
53-
title: "Tears of Steel",
54-
description: "Tears of Steel",
55-
poster: "https://cdn.theoplayer.com/video/tears_of_steel/poster.jpg"
56-
}
57-
}
52+
title: 'Tears of Steel',
53+
description: 'Tears of Steel',
54+
poster: 'https://cdn.theoplayer.com/video/tears_of_steel/poster.jpg',
55+
},
56+
},
5857
];
5958

6059
// the desired source is set in the player -
@@ -70,12 +69,12 @@ var playlist = [
7069
function firstplaying() {
7170
player.clip.startTime = player.source.sources.startTime;
7271
player.clip.endTime = player.source.sources.endTime;
73-
THEOplayer.players[0].removeEventListener("durationchange", firstplaying);
72+
THEOplayer.players[0].removeEventListener('durationchange', firstplaying);
7473
}
7574

76-
THEOplayer.players[0].addEventListener("sourcechange", function () {
77-
THEOplayer.players[0].removeEventListener("durationchange", firstplaying);
78-
THEOplayer.players[0].addEventListener("durationchange", firstplaying);
75+
THEOplayer.players[0].addEventListener('sourcechange', function () {
76+
THEOplayer.players[0].removeEventListener('durationchange', firstplaying);
77+
THEOplayer.players[0].addEventListener('durationchange', firstplaying);
7978
});
8079
```
8180

‎theoplayer/faq/40-can-we-use-hls-or-dash-ads.md

+8-8
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,14 @@ To be able to play HLS or DASH advertisements, make sure to add `allowedMimeType
88
new THEOplayer.Player(element, {
99
ads: {
1010
allowedMimeTypes: [
11-
"application/dash+xml",
12-
"application/x-mpegURL",
13-
"application/vnd.apple.mpegurl",
14-
"video/mp4",
15-
"video/3gpp", // See the Remark about 3gpp at the bottom.
16-
"video/webm"
17-
]
18-
}
11+
'application/dash+xml',
12+
'application/x-mpegURL',
13+
'application/vnd.apple.mpegurl',
14+
'video/mp4',
15+
'video/3gpp', // See the Remark about 3gpp at the bottom.
16+
'video/webm',
17+
],
18+
},
1919
});
2020
```
2121

‎theoplayer/faq/47-can-we-show-custom-message-on-403-on-mp4.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ function reqListener() {
2020
XMLHttpRequestObject = this;
2121
}
2222
requestObject = new XMLHttpRequest();
23-
requestObject.addEventListener("load", reqListener);
24-
requestObject.open("GET", "https://httpstat.us/403?sleep=100");
23+
requestObject.addEventListener('load', reqListener);
24+
requestObject.open('GET', 'https://httpstat.us/403?sleep=100');
2525
requestObject.send();
2626

2727
XMLHttpRequestObject.status; // result should be 403 - this may be used for a control that, if true, prints on the overlay the desired error message.

‎theoplayer/faq/52-is-it-a-problem-if-viewer-pauses-live-stream-longer-than-dvr-window.md

+2-5
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,7 @@ In case you wish to avoid this behavior and skip the current buffer, this is als
99
This is a JavaScript example for this, where the DVR window is 60 sec long and the new custom position to seek to is in the middle of it.
1010

1111
```js
12-
player.addEventListener("play", () => {
13-
player.currentTime =
14-
player.seekable.end() - player.currentTime > 60
15-
? player.seekable.end() - 30
16-
: player.currentTime;
12+
player.addEventListener('play', () => {
13+
player.currentTime = player.seekable.end() - player.currentTime > 60 ? player.seekable.end() - 30 : player.currentTime;
1714
});
1815
```

‎theoplayer/faq/55-how-to-track-network-errors.md

+6-9
Original file line numberDiff line numberDiff line change
@@ -12,17 +12,17 @@ function httpErrorInterceptor(response) {
1212
var errorDetails = {
1313
status: response.status,
1414
fileType: response.request.type,
15-
url: response.request.url
15+
url: response.request.url,
1616
};
17-
var networkErrorEvent = new CustomEvent("THEOnetworkerror", {
18-
detail: errorDetails
17+
var networkErrorEvent = new CustomEvent('THEOnetworkerror', {
18+
detail: errorDetails,
1919
});
2020
document.dispatchEvent(networkErrorEvent);
2121
}
2222
}
2323

2424
player.network.addResponseInterceptor(httpErrorInterceptor);
25-
document.addEventListener("THEOnetworkerror", console.log);
25+
document.addEventListener('THEOnetworkerror', console.log);
2626
```
2727

2828
## Android
@@ -40,12 +40,9 @@ For Android, you'll also use the Network API as you would with our Web SDK but y
4040
var errorDetails = {
4141
status: response.status,
4242
fileType: response.request.type,
43-
url: response.request.url
43+
url: response.request.url,
4444
};
45-
theoplayerAndroid.sendMessage(
46-
"THEOplayer.network.error",
47-
JSON.stringify(errorDetails)
48-
);
45+
theoplayerAndroid.sendMessage('THEOplayer.network.error', JSON.stringify(errorDetails));
4946
}
5047
};
5148
player.network.addResponseInterceptor(interceptor);

‎theoplayer/faq/58-how-to-apply-accurate-buffering-strategy.md

+3-9
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ The below table presents what approximately bandwidth is required for video stre
2121
Taking above table into account, the logic responsible for the proactive strategy can look like:
2222

2323
```javascript
24-
player.addEventListener("representationchange", function (event) {
24+
player.addEventListener('representationchange', function (event) {
2525
// specifies how big bandwidth is required for the current quality
2626
var representationBandwidth = event.representation.bandwidth;
2727
// player.abr.targetBuffer is 20 by default
@@ -30,10 +30,7 @@ player.addEventListener("representationchange", function (event) {
3030
// SD
3131
if (representationBandwidth < 3000000) {
3232
targetBuffer = 20;
33-
} else if (
34-
representationBandwidth > 3000000 &&
35-
representationBandwidth < 6000000
36-
) {
33+
} else if (representationBandwidth > 3000000 && representationBandwidth < 6000000) {
3734
// HD
3835
targetBuffer = 10;
3936
} else if (representationBandwidth > 6000000) {
@@ -42,10 +39,7 @@ player.addEventListener("representationchange", function (event) {
4239
}
4340

4441
player.abr.targetBuffer = targetBuffer;
45-
console.log(
46-
"representationchange - updated player.abr.targetBuffer: " +
47-
player.abr.targetBuffer
48-
);
42+
console.log('representationchange - updated player.abr.targetBuffer: ' + player.abr.targetBuffer);
4943
});
5044
```
5145

‎theoplayer/faq/64-page-and-source-domains.md

+2-4
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,7 @@ Page and Source domains prevent unauthorized users from embedding your SDK on th
44

55
## Page domains
66

7-
8-
9-
Page domains (available only on Web SDK, React Native SDK and Flutter SDK) specify on which domains the player can be loaded.
7+
Page domains (available only on Web SDK, React Native SDK and Flutter SDK) specify on which domains the player can be loaded.
108

119
Imagine your website has the following domain: `example.com`, you have configured your Page domains and the THEOplayer SDK is installed on your website. When a malicious user copies your SDK and installs it on their domain, `other.com`, the player will throw an error that the license is invalid.
1210

@@ -24,4 +22,4 @@ Your source domains are included on your player [license](https://www.theoplayer
2422

2523
## How to configure Page and Source domains
2624

27-
Page and Source domains can be configured in the [Developer Portal](https://portal.theoplayer.com) when creating a license or a custom SDK. On an existing license/SDK, you can find the Page and Source domains under the “Configure” section of the SDK overview page. The “Allow all” option can be selected when you are not certain on which domains the player will be loaded or from which domains the player will play streams. This option is separately configurable for both Page and Source domains.
25+
Page and Source domains can be configured in the [Developer Portal](https://portal.theoplayer.com) when creating a license or a custom SDK. On an existing license/SDK, you can find the Page and Source domains under the “Configure” section of the SDK overview page. The “Allow all” option can be selected when you are not certain on which domains the player will be loaded or from which domains the player will play streams. This option is separately configurable for both Page and Source domains.

‎theoplayer/faq/66-Why-is-my-Playready-stream-not-working-in-Chromium-Edge.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ In 2.78, we fixed an issue that was preventing specific streams to play in Edge
1111
We noticed that, due to their default settings, a conflict arises (regarding which DRM system is to be given priority) between the player and the browser. This may lead to playback failure for certain PlayReady streams. This is solved directly on the implementer’s side by using the following values order for the _preferredKeySystems_ property.
1212

1313
```js
14-
preferredKeySystems: ["playready", "widevine", "fairplay"];
14+
preferredKeySystems: ['playready', 'widevine', 'fairplay'];
1515
```
1616

1717
Please note that this will not hinder playback in case also/only Widevine is present, nor on other browsers.

0 commit comments

Comments
 (0)