@brightspace-ui/labs 2.35.2 → 2.36.1

package/package.json

@@ -114,5 +114,5 @@
     "resize-observer-polyfill": "^1",
     "webvtt-parser": "^2.1.2"
   },
-  "version": "2.35.2"
+  "version": "2.36.1"
 }

package/src/components/ou-filter/tree-filter.js

@@ -755,17 +755,20 @@ class TreeFilter extends LocalizeLabsElement(MobxLitElement) {
 	_renderChildren(id, parentName, indentLevel = 0) {
 		parentName = parentName || this.localize('components:ouFilter:treeFilter:nodeName:root');
 
-		if (id === undefined || this.tree.getChildIdsForDisplay(id).length === 0) {
-			return html`<d2l-empty-state-simple
-				slot="tree"
-				description="${this.localize('components:ouFilter:treeSelector:noFiltersAvailable')}"
-			>
-			</d2l-empty-state-simple>`;
+		const emptyState = html`<d2l-empty-state-simple
+			slot="tree"
+			description="${this.localize('components:ouFilter:treeSelector:noFiltersAvailable')}"
+		></d2l-empty-state-simple>`;
+
+		if (id === undefined) {
+			return emptyState;
 		}
 
 		if (!this.tree.isPopulated(id)) {
 			// request children; in the meantime we can render whatever we have
 			this._requestChildren(id);
+		} else if (this.tree.getChildIdsForDisplay(id).length === 0) {
+			return emptyState;
 		}
 
 		return [

package/src/utilities/router/README.md

@@ -184,6 +184,15 @@ import { navigate } from '@brightspace-ui/labs/utilities/lit-router';
 navigate('/my-app/new-place');
 ```
 
+navigate can also be used to pass data between views. This is useful for sharing state objects between views without needing to make additional server calls. If the data you are sharing with a view is part of the state of the next view consider using a search param instead.
+
+```js
+import { navigate } from '@brightspace-ui/labs/utilities/lit-router';
+
+navigate(`/users?userId=${userId}`, { data: { /* sharing the user object here so I don't need to fetch it again */ } });
+```
+
+
 To redirect to a page and replace the previous browser history item the new one, use `redirect(path)`:
 
 ```js
@@ -224,4 +233,4 @@ describe('Page Routing', () => {
 
 This issue is resolved by default but the fix can be bypassed (for backwards compatibility) by setting the `disableRouteOrderFix` option to `true`.
 
-Bypassing the fix causes a warning to appear in the dev console. To resolve the warning, remove the `disaableRouteOrderFix` option and thoroughly test your routing. If your routes contain wildcards (`*`, typically for 404s), you may need to register them last.
+Bypassing the fix causes a warning to appear in the dev console. To resolve the warning, remove the `disaableRouteOrderFix` option and thoroughly test your routing. If your routes contain wildcards (`*`, typically for 404s), you may need to register them last.

package/src/utilities/router/router.js

@@ -3,6 +3,7 @@ import page from 'page';
 let activePage = page;
 let _lastOptions = {};
 let _lastContext = {};
+let passedData = undefined;
 
 export const _createReducedContext = pageContext => ({
 	params: pageContext.params,
@@ -13,6 +14,7 @@ export const _createReducedContext = pageContext => ({
 	route: pageContext.routePath,
 	title: pageContext.title,
 	options: {},
+	passedData
 });
 
 const _storeCtx = () => {
@@ -27,7 +29,9 @@ const _handleRouteView = (context, next, r) => {
 		const reducedContext = _createReducedContext(context);
 		context.view = (host, options) => {
 			reducedContext.options = options || {};
-			return r.view.call(host, reducedContext);
+			const resultingView = r.view.call(host, reducedContext);
+			passedData = undefined;
+			return resultingView;
 		};
 		context.handled = true;
 
@@ -118,7 +122,9 @@ const addMiddleware = callback => {
 
 // Triggers navigation to the specified route path.
 // Creates a new entry in the browser's history stack.
-export const navigate = path => {
+// data in the options object is available to the next view in ctx.passedData
+export const navigate = (path, options) => {
+	passedData = options?.data;
 	activePage.show(path);
 };