Merge branch 'dev' into feature/accessibility-colorshift

Author: michielvandergeest

CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## v5.0.0
+
+*22 aug 2022*
+
+- Moved Metrological and Platform specific plugins to [metrological-sdk](https://github.com/Metrological/metrological-sdk) (Metedata, Metrics, Pin, Profile, Purchase, TV, VideoPlayer)
+- Added base 64 image support for Image plugin
+- Fixed bug in Image plugin as Img cover stretches image
+- Fixed named route property not being accessed properly
+- Added/Updated Router available methods
+
+
 ## v4.8.3
 
 *19 apr 2022*

docs/_sidebar.md

@@ -8,7 +8,6 @@
   - [Log](/plugins/log.md)
   - [Metadata](/plugins/metadata.md)
   - [Metrics](/plugins/metrics.md)
-  - [Metadata](/plugins/metadata.md)
   - [Profile](/plugins/profile.md)
   - [Purchase](/plugins/purchase.md)
   - [Language](/plugins/language.md)

docs/changelog.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## v5.0.0
+
+*22 aug 2022*
+
+- Moved Metrological and Platform specific plugins to [metrological-sdk](https://github.com/Metrological/metrological-sdk) (Metedata, Metrics, Pin, Profile, Purchase, TV, VideoPlayer)
+- Added base 64 image support for Image plugin
+- Fixed bug in Image plugin as Img cover stretches image
+- Fixed named route property not being accessed properly
+- Added/Updated Router available methods
+
+
 ## v4.8.3
 
 *19 apr 2022*

docs/index.md

@@ -6,20 +6,33 @@ The Reference Documentation for Lightning SDK contains detailed descriptions of
 
 The available Lightning SDK plugins are, in alphabetical order:
 
+<!---TOC_start--->
+* [Colors](plugins/colors.md)
 * [FPS Counter](plugins/fpscounter.md)
 * [Image](plugins/image.md)
 * [Language](plugins/language.md)
 * [Lightning](plugins/lightning.md)
 * [Log](plugins/log.md)
+* [Metadata](plugins/metadata.md)
 * [Metrics](plugins/metrics.md)
 * [Pin](plugins/pin.md)
 * [Profile](plugins/profile.md)
 * [Purchase](plugins/purchase.md)
 * [Registry](plugins/registry.md)
 * [Router](plugins/router/index.md)
+  * [Configuration](plugins/router/configuration.md)
+  * [Navigation](plugins/router/navigation.md)
+  * [Data Providing](plugins/router/dataproviding.md)
+  * [Router Events](plugins/router/events.md)
+  * [Page Transitions](plugins/router/pagetransitions.md)
+  * [Widgets](plugins/router/widgets.md)
+  * [Settings](plugins/router/settings.md)
+  * [Deeplinking](plugins/router/deeplinking.md)
+  * [History](plugins/router/history.md)
 * [Settings](plugins/settings.md)
 * [Storage](plugins/storage.md)
 * [TV](plugins/tv.md)
 * [Utils](plugins/utils.md)
 * [VersionLabel](plugins/versionlabel.md)
 * [VideoPlayer](plugins/videoplayer.md)
+<!---TOC_end--->

docs/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lightningjs/sdk",
-  "version": "4.8.3",
+  "version": "5.0.0",
   "license": "Apache-2.0",
   "scripts": {
     "postinstall": "node ./scripts/postinstall.js",
@@ -23,6 +23,7 @@
   "dependencies": {
     "@babel/polyfill": "^7.11.5",
     "@lightningjs/core": "*",
+    "@metrological/sdk": "github:metrological/metrological-sdk",
     "@michieljs/execute-as-promise": "^1.0.0",
     "deepmerge": "^4.2.2",
     "localCookie": "github:WebPlatformForEmbedded/localCookie",

docs/plugins/colors/index.md

@@ -4,74 +4,4 @@ If you create an App, you store the App's *metadata* (such as its name, version
 
 The Metadata plugin enables you to use this metadata in your App. (For example, if you want to show the App's version number in an *About* window.)
 
-> If you deploy your App to the Metrological Store, the metadata is 'injected' into the App by the Metrological Store.
-
-## Usage
-
-If you want to access metadata in your App code directly, import the *Metadata* plugin from the Lightning SDK:
-
-```js
-import { Metadata } from '@lightningjs/sdk'
-```
-
-The SDK automatically creates the `appMetadata`  from the Launch params.
-
-## Available methods
-
-### Get
-
-Returns the key value of the metadata.
-
-```js
-Metadata.get(key, [fallback])
-```
-Key can be either `icon`, `id`, `safeId`, `version`, `name`, `description`, `type`, `url` or `artwork` .
-Optionally you can specify a `fallback`-value for when the Metadata is not defined.
-
-### AppId
-
-Gets Application id from Metadata
-
-```js
-Metadata.appId()
-```
-
-### SafeAppId
-
-Returns the *safe ID* of your App. This is actually the `AppId` without dots (and any other special characters) which are are not permitted in JS variables.
-
-```js
-Metadata.safeAppId()
-```
-
-### AppName
-
-Returns the name of your App.
-
-```js
-Metadata.appName()
-```
-
-### AppVersion
-
-Returns the version of your App (without the GIT commit hash).
-
-```js
-Metadata.appVersion()
-```
-
-### AppIcon
-
-Returns the icon of your App.
-
-```js
-Metadata.appIcon()
-```
-
-### AppFullVersion
-
-Returns the full version of your App.
-
-```js
-Metadata.appFullVersion()
-```
+> Starting <i>v5.0.0</i> and up, the Metadata plugin is part of the <b>metrological-sdk</b>.<br /><br />For backwards compatibility reasons, the Lightning-SDK exports this plugin provided by the metrological-sdk. The code however is maintained <a href="https://github.com/Metrological/metrological-sdk" target="_blank">here</a>. More information on how to use this plugin can be found <a href="https://github.com/Metrological/metrological-sdk/blob/master/docs/plugins/metadata.md" target="_blank">here</a>.