wip: missed merge changes

Author: Julusian

.github/workflows/node.yaml

@@ -758,6 +758,6 @@ jobs:
           CI: true
       - name: Run check
         run: |
-          node scripts/checkForMultipleVersions.mjs
+          yarn validate:versions
         env:
           CI: true

package.json

@@ -25,7 +25,7 @@
 		"meteor:run": "cd meteor && yarn start",
 		"lint": "run lint:meteor && run lint:packages",
 		"unit": "run unit:meteor && run unit:packages",
-		"validate:release": "yarn install && run install-and-build && run validate:release:packages && run validate:release:meteor",
+		"validate:release": "yarn install && run install-and-build && run validate:versions && run validate:release:packages && run validate:release:meteor",
 		"validate:release:meteor": "cd meteor && yarn validate:prod-dependencies && yarn license-validate && yarn lint && yarn test",
 		"validate:release:packages": "cd packages && run validate:dependencies && run test",
 		"meteor": "cd meteor && meteor",

packages/documentation/docs/for-developers/url-query-parameters.md

@@ -0,0 +1,24 @@
+---
+sidebar_label: URL Query Parameters
+sidebar_position: 10
+---
+
+# URL Query Parameters
+Appending query parameter(s) to the URL will allow you to modify the behaviour of the GUI, as well as control the [Access Levels](../user-guide/features/access-levels.md).
+
+| Query Parameter                     | Description                                                               |
+| :---------------------------------- | :------------------------------------------------------------------------ |
+| `admin=1` | Gives the GUI the same access as the combination of [Configuration Mode](../user-guide/features/access-levels.md#Configuration-Mode) and [Studio Mode](../user-guide/features/access-levels.md#Studio-Mode) as well as having access to a set of [Testing Mode](../user-guide/features/access-levels.md#Testing-Mode) tools and a Manual Control section on the Rundown page. _Default value is `0`._ | 
+| `studio=1` | [Studio Mode](../user-guide/features/access-levels.md#Studio-Mode) gives the GUI full control of the studio and all information associated to it. This includes allowing actions like activating and deactivating rundowns, taking parts, adlibbing, etcetera. _Default value is `0`._ | 
+| `buckets=0,1,...`                  | The buckets can be specified as base-0 indices of the buckets as seen by the user. This means that `?buckets=1` will display the second bucket as seen by the user when not filtering the buckets. This allows the user to decide which bucket is displayed on a secondary attached screen simply by reordering the buckets on their main view. |
+| `develop=1` | Enables the browser's default right-click menu to appear. It will also reveal the _Manual Control_ section on the Rundown page. _Default value is `0`._ |
+| `display=layout,buckets,inspector` | A comma-separated list of features to be displayed in the shelf. Available values are: `layout` \(for displaying the Rundown Layout\), `buckets` \(for displaying the Buckets\) and `inspector` \(for displaying the Inspector\).           |
+| `help=1` | Enables some tooltips that might be useful to new users. _Default value is `0`._ | 
+| `ignore_piece_content_status=1` | Removes the "zebra" marking on VT pieces that have a "missing" status. _Default value is `0`._ | 
+| `reportNotificationsId=1,...` | Sets a specific ID of the client GUI. Useful for troubleshooting since this ID shows up in _Sofie Core_'s log.  _Default value is "0", which disables the feature and uses a user-defined string (user as-in whoever is opening the client GUI, not necessarily the actual end-user)._  |  
+| `shelffollowsonair=1` | _Default value is `0`._ | 
+| `show_hidden_source_layers=1` | _Default value is `0`._ | 
+| `speak=1` | Experimental feature that starts playing an audible countdown 10 seconds before each planned _Take_. _Default value is `0`._ | 
+| `vibrate=1` | Experimental feature that triggers the vibration API in the web browser 3 seconds before each planned _Take_. _Default value is `0`._ | 
+| `zoom=1,...` | Sets the scaling of the entire GUI. _The unit is a percentage where `100` is the default scaling._ | 
+

packages/documentation/docs/user-guide/features/access-levels.md

@@ -40,20 +40,24 @@ There are some additional url parameters that can be used to simplify the granti
 - `?help=1` will enable some tooltips that might be useful to new users.
 - `?admin=1` will give the user the same access as the _Configuration_ and _Studio_ modes as well as having access to a set of _Test Tools_ and a _Manual Control_ section on the Rundown page.
 
+#### See Also
+
+[URL Query Parameters](../../for-developers/url-query-parameters.md)
+
 ### Header based
 
 :::danger
 
-This mode is very new and could have some undiscovered holes.  
+This mode is very new and could have some undiscovered holes.
 It is known that secrets can be leaked to all clients who can connect to Sofie, which is not desirable.
 
 :::
 
-In this mode, we rely on Sofie being run behind a reverse-proxy which will inform Sofie of the permissions of each connection. This allows you to use your organisations preferred auth provider, and translate that into something that Sofie can understand.  
+In this mode, we rely on Sofie being run behind a reverse-proxy which will inform Sofie of the permissions of each connection. This allows you to use your organisations preferred auth provider, and translate that into something that Sofie can understand.
 To enable this mode, you need to enable the `enableHeaderAuth` property in the [settings file](../configuration/sofie-core-settings.md)
 
-Sofie expects that for each DDP connection or http request, the `dnt` header will be set containing a comma separated list of the levels from the above table. If the header is not defined or is empty, the connection will have view-only access to Sofie.  
-This header can also contain simply `admin` to grant the connection permission to everything.  
+Sofie expects that for each DDP connection or http request, the `dnt` header will be set containing a comma separated list of the levels from the above table. If the header is not defined or is empty, the connection will have view-only access to Sofie.
+This header can also contain simply `admin` to grant the connection permission to everything.
 We are using the `dnt` header due to limitations imposed by Meteor, but intend this to become a proper header name in a future release.
 
 When in this mode, you should make sure that Sofie can only be accessed through the reverse proxy, and that the reverse-proxy will always override any value sent by a client.

packages/openapi/package.json

@@ -1,7 +1,6 @@
 {
 	"name": "@sofie-automation/openapi",
 	"version": "1.52.0-in-development",
-	"private": true,
 	"license": "MIT",
 	"repository": {
 		"type": "git",

packages/package.json

@@ -19,7 +19,7 @@
 		"build": "lerna run build --ignore @sofie-automation/openapi",
 		"build:try": "lerna run --no-bail build --ignore @sofie-automation/openapi",
 		"watch": "lerna run --parallel build:main --ignore @sofie-automation/openapi -- --watch --preserveWatchOutput",
-		"stage-versions": "git add -u */package.json */CHANGELOG.md lerna.json yarn.lock",
+		"stage-versions": "git add -u \"*/package.json\" \"*/CHANGELOG.md\" lerna.json yarn.lock",
 		"set-version": "lerna version --exact --no-changelog --no-git-tag-version --no-push --yes",
 		"set-version-and-commit": "lerna version --exact --no-changelog --no-changelog --no-commit-hooks --force-publish='*' --no-push --yes",
 		"set-version-and-changelog": "lerna version --exact --force-publish --conventional-commits --no-git-tag-version --no-push --yes",

packages/webui/src/client/collections/index.ts

@@ -41,7 +41,7 @@ import { RundownBaselineAdLibAction } from '@sofie-automation/corelib/dist/dataM
 import { RundownBaselineAdLibItem } from '@sofie-automation/corelib/dist/dataModel/RundownBaselineAdLibPiece'
 import { DBRundownPlaylist } from '@sofie-automation/corelib/dist/dataModel/RundownPlaylist'
 import { DBSegment } from '@sofie-automation/corelib/dist/dataModel/Segment'
-import { DBNotificationObj } from '@sofie-automation/corelib/dist/dataModel/Notifications'
+import type { DBNotificationObj } from '@sofie-automation/corelib/dist/dataModel/Notifications'
 
 export const AdLibActions = createSyncReadOnlyMongoCollection<AdLibAction>(CollectionName.AdLibActions)
 

scripts/checkForMultipleVersions.mjs

@@ -1,5 +1,12 @@
 import { buildDepTreeFromFiles } from "snyk-nodejs-lockfile-parser";
 
+function hr() {
+	// write regular dashes if this is a "simple" output stream ()
+	if (!process.stdout.hasColors || !process.stdout.hasColors())
+		return "-".repeat(process.stdout.columns ?? 40);
+	return '─'.repeat(process.stdout.columns ?? 40)
+}
+
 /**
  * These are the libs we want to consider.
  * Its an array of arrays, to allow for multiple names to be treated as one package
@@ -58,6 +65,10 @@ await addDepsForRoot("./packages", "live-status-gateway");
 
 let hasFailure = false;
 
+console.log(hr())
+console.log(" 🔢 Checking dependency version consistency...")
+console.log(hr())
+
 // check each library
 for (const libName of libsToConsider) {
 	const allVersions = new Set();
@@ -73,11 +84,11 @@ for (const libName of libsToConsider) {
 	// output some info
 	const str = Array.from(allVersions).join(", ");
 	if (allVersions.size === 0) {
-		console.log(`No versions of "${nameStr}" installed`);
+		console.log(`❔ No versions of "${nameStr}" installed`);
 	} else if (allVersions.size === 1) {
-		console.log(`Single version of "${nameStr}" installed: ${str}`);
+		console.log(`✅ Single version of "${nameStr}" installed: ${str}`);
 	} else {
-		console.error(`Multiple versions of "${nameStr}" installed: ${str}`);
+		console.error(`⚠️ Multiple versions of "${nameStr}" installed: ${str}`);
 		hasFailure = true;
 	}
 }