@conduction/nextcloud-vue 1.0.0-beta.19 → 1.0.0-beta.20

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@conduction/nextcloud-vue",
-	"version": "1.0.0-beta.19",
+	"version": "1.0.0-beta.20",
 	"description": "Shared Vue component library for Conduction Nextcloud apps — complements @nextcloud/vue with higher-level components, OpenRegister integration, and NL Design System support",
 	"license": "EUPL-1.2",
 	"author": "Conduction B.V. <info@conduction.nl>",

package/src/components/CnPageRenderer/CnPageRenderer.vue

@@ -219,13 +219,28 @@ export default {
 			return component
 		},
 		/**
-		 * Props forwarded to the dispatched page component. Spreads the
-		 * page's `config` object so manifest authors can supply whatever
-		 * shape the target page expects. Intentionally generic — per-type
-		 * prop validation lives on the target components themselves.
+		 * Props forwarded to the dispatched page component. Merges:
+		 *
+		 *   1. The page's static `config` object — manifest-authored data
+		 *      shared across every visit to this route.
+		 *   2. The router's `$route.params` — dynamic placeholders captured
+		 *      from the URL (e.g. `/meetings/:id/live` → `{ id: '...' }`).
+		 *      Without this merge, children that declare a route-derived
+		 *      prop (`props: { id: { type: String, required: true } }`)
+		 *      receive `undefined` even when the URL clearly contains the
+		 *      value, because the generated route definition's `props: true`
+		 *      only binds params to `CnPageRenderer` itself, not the
+		 *      dispatched child component. Params take precedence over
+		 *      `config` collisions so URL truth wins; config keeps acting
+		 *      as a default-overrides layer.
+		 *
+		 * Per-type prop validation lives on the target components.
 		 */
 		resolvedProps() {
-			return this.currentPage?.config ?? {}
+			return {
+				...(this.currentPage?.config ?? {}),
+				...(this.$route?.params ?? {}),
+			}
 		},
 		/**
 		 * Combined slot-override map for the dispatched page component.