Renamed to MediaURL

Author: MediaURL1

Diff for: .github/ISSUE_TEMPLATE/watched-issue--idea-or-request.md

@@ -1,16 +1,15 @@
 ---
-name: WATCHED issue, idea or request
-about: Anything related to the WATCHED SDK or our app
-title: ''
-labels: ''
-assignees: ''
-
+name: MediaURL issue, idea or request
+about: Anything related to the MediaURL SDK or our app
+title: ""
+labels: ""
+assignees: ""
 ---
 
 Please describe your issue in as much detail as possible.
 
-- **Only** post issues related to the WATCHED app or the WATCHED SDK.
+- **Only** post issues related to the MediaURL SDK.
 
 - We do **not** give support for **3rd party addons**. Try to contact the addon creator.
 
-- If you have an issue with one of [official addons](https://github.com/watchedcom) create an issue in the corresponding repo.
+- If you have an issue with one of [official addons](https://github.com/mediaurl) create an issue in the corresponding repo.

Diff for: CHANGELOG.md

@@ -6,7 +6,7 @@
 
 - Added `SetResultError` to set cache results in a different way. For more infos, see the code documentation.
 - Added IPTV category property and default filter values
-- Removed the `@watchedcom/create` package
+- Removed the `@mediaurl/create` package
 - Removed the `watched-sdk` command line tool
 - Added experimental `FetchAgent`
 
@@ -17,7 +17,7 @@
 - Dropping legacy Node.js versions (=> 12.9 is now required)
 - Added similar item system for items. See the `similarItem` property. Similar items will be displayed as horizontal lists below movie, series or channel items.
 - Created `toast` task to display toast messages inside the app (see `ctx.toast`)
-- Created `notification` task to display notifications with various options inside the app (see `ctx.notification`). Notifications can be displayed once every 30 minute per addon. You can set the `url` property to open an URL when the user clicks on the notification. WATCHED sharing URL's are handled internally, so you can promote for example an item or addon.
+- Created `notification` task to display notifications with various options inside the app (see `ctx.notification`). Notifications can be displayed once every 30 minute per addon. You can set the `url` property to open an URL when the user clicks on the notification. MediaURL sharing URL's are handled internally, so you can promote for example an item or addon.
 - Various bugfixes and improvments
 
 ### Upgrade instructions
@@ -45,8 +45,8 @@ with
 ### Legacy
 
 - The `watched-sdk` command line tool will be legacy starting with v0.32
-- The [`@watchedcom/create`](packages/create) command line tool is printing a legacy message
-- The `testAddon` function in [`@watchedcom/test`](packages/test) is printing a legacy message when it's used
+- The [`@mediaurl/create`](packages/create) command line tool is printing a legacy message
+- The `testAddon` function in [`@mediaurl/test`](packages/test) is printing a legacy message when it's used
 
 ### Upgrade instructions
 
@@ -74,7 +74,7 @@ Since the `watched-sdk` command is legacy, you can't export your addons anymore.
 - **`src/index.ts`**
 
   ```ts
-  import { runCli } from "@watchedcom/sdk";
+  import { runCli } from "@mediaurl/sdk";
 
   // Your code here
 

Diff for: README.md

@@ -1,10 +1,10 @@
-# WATCHED.com SDK and tools
+# MediaURL SDK and tools
 
-This monorepo includes all javascript modules needed to create addons for [WATCHED](https://www.watched.com/).
+This monorepo includes all javascript modules needed to create _MediaURL_ addons.
 
 ## Getting started
 
-In best way to create your own WATCHED addon is by cloning our example addon and modify it.
+In best way to create your own MediaURL addon is by cloning our example addon and modify it.
 
 ### Prerequisites
 
@@ -14,10 +14,10 @@ In best way to create your own WATCHED addon is by cloning our example addon and
 
 ### Cloning the example addon
 
-The best way to start is to clone our [watched-addon-example](https://github.com/watchedcom/watched-addon-example) addon:
+The best way to start is to clone our [mediaurl-addon-example](https://github.com/mediaurl/mediaurl-addon-example) addon:
 
 ```shell
-git clone https://github.com/watchedcom/watched-addon-example.git my-addon
+git clone https://github.com/mediaurl/mediaurl-addon-example.git my-addon
 ```
 
 Now open the created folder `my-addon` with your editor.
@@ -37,7 +37,7 @@ npm run develop
 You should see something like this:
 
 ```
-> watched[email protected] develop /home/myname/my-addon
+> mediaurl[email protected] develop /home/myname/my-addon
 > ts-node-dev --transpileOnly src
 
 Using ts-node version 8.9.1, typescript version 3.8.3
@@ -48,9 +48,9 @@ Listening on 3000
 
 **2. Enable developer mode**
 
-In order to install addons in the WATCHED app, you first need to _unlock_ it:
+In order to install addons in the MediaURL app, you first need to _unlock_ it:
 
-1. Open the WATCHED app, go to settings and make sure the **Developer mode** is enabled.
+1. Open the MediaURL app, go to settings and make sure the **Developer mode** is enabled.
 2. Go to the addon manager and deactivate the bundle addon if there is one active.
 3. To make things more clean and easy, disabled all currently activated addons.
 
@@ -88,7 +88,7 @@ Please also check out our object schema here: https://www.watched.com/swagger
 
 ## Deploy your addon
 
-Please check our deployment documentation at [docs/deployment.md](https://github.com/watchedcom/watched-js/blob/master/docs/deployment.md).
+Please check our deployment documentation at [docs/deployment.md](https://github.com/mediaurl/mediaurl-js/blob/master/docs/deployment.md).
 
 ## Tips for development and testing
 
@@ -121,7 +121,7 @@ npm run develop -- replay test-session --watch
 Create a test case file, for example `src/record.test.ts`:
 
 ```javascript
-import { replayRecordFile } from "@watchedcom/sdk";
+import { replayRecordFile } from "@mediaurl/sdk";
 import { yourAddon } from "./index";
 
 test(`Replay recorded actions`, (done) => {
@@ -143,7 +143,7 @@ We offer a very flexible caching solution for your addon. Please see [docs/cachi
 
 ## Translate your addon
 
-For some suggestions regarding translations, please see either our `@watchedcom/i18n` package found inside [packages/i18n](packages/i18n), or the documentation at [docs/translations.md](docs/translations.md).
+For some suggestions regarding translations, please see either our `@mediaurl/i18n` package found inside [packages/i18n](packages/i18n), or the documentation at [docs/translations.md](docs/translations.md).
 
 ## Developing on this repo
 

Diff for: docs/caching.md

@@ -19,7 +19,7 @@ A cache which uses the file system for storage. This is the most easy to setup c
 To enable this, set the environment variable `DISK_CACHE` to a path.
 
 ```shell
-export DISK_CACHE=/data/watched-cache
+export DISK_CACHE=/data/mediaurl-cache
 npm run develop
 ```
 

Diff for: docs/deployment.md

@@ -1,6 +1,6 @@
 # Deployment guide
 
-Instructions on how to deploy a WATCHED addon to various hosting providers.
+Instructions on how to deploy a MediaURL addon to various hosting providers.
 
 - [Heroku](#Heroku)
 
@@ -37,7 +37,7 @@ Go to your addon directory, then run the following code:
 
 ```shell
 # Add files related to vercel
-$ npx @watchedcom/create init-vercel
+$ npx @mediaurl/create init-vercel
 
 # Link project
 $ now

Diff for: docs/translations.md

@@ -18,7 +18,7 @@ This type supports either a string of text, or a mapping of language=>text pairs
 }
 ```
 
-## Using `@watchedcom/i18n`
+## Using `@mediaurl/i18n`
 
 Short after this documentation was written, I created a little helper module for `i18next`. Please see the documentation at `packages/i18n/README.md`.
 
@@ -43,7 +43,7 @@ i18next.use(
   new FsBackend(null, {
     loadPath: path.join("locales", "{{lng}}", "{{ns}}.json"),
     addPath: path.join("locales", "{{lng}}", "{{ns}}.missing.json"),
-    jsonIndent: 2
+    jsonIndent: 2,
   })
 );
 
@@ -55,7 +55,7 @@ i18next.init({
   defaultNS: "your-addon-id",
   load: "languageOnly",
   saveMissing: true,
-  updateMissing: true
+  updateMissing: true,
 });
 
 export const i18n = i18next;
@@ -143,23 +143,23 @@ After this you can deploy your addon without using locize. This has many benefit
 Imagine you want to translate the `name` property of this addon:
 
 ```javascript
-import { createWorkerAddon } from "@watchedcom/sdk";
+import { createWorkerAddon } from "@mediaurl/sdk";
 
 export const myAddon = createWorkerAddon({
   id: "i18n-example",
-  name: "Name of this addon"
+  name: "Name of this addon",
 });
 ```
 
 We created a helper function named `translateDeep` for cases like this. This function works similar to the `lodash.cloneDeep` function, but translates all strings beginning with a specific prefix (by default `i18n:`) using the `t` parameter.
 
 ```javascript
-import { createWorkerAddon, translateDeep } from "@watchedcom/sdk";
+import { createWorkerAddon, translateDeep } from "@mediaurl/sdk";
 import { i18n } from "./i18n";
 
 export const myAddon = createWorkerAddon({
   id: "i18n-example",
-  name: "i18n:Name of this addon"
+  name: "i18n:Name of this addon",
 });
 
 myAddon.registerActionHandler("addon", async (input, ctx, addon) => {

Diff for: package-lock.json

@@ -1,5 +1,5 @@
-# WATCHED SDK example addon
+# MediaURL SDK example addon
 
 This example repository is more for testing the SDK inside this monorepo than for a real world example.
 
-If you are looking for a good example addon, please check out the [watched-addon-example](https://github.com/watchedcom/watched-addon-example) repository.
+If you are looking for a good example addon, please check out the [mediaurl-addon-example](https://github.com/mediaurl/mediaurl-addon-example) repository.