From 22d96e1904b920d449f1857fe3caf82862fe7d56 Mon Sep 17 00:00:00 2001
From: Alex Eagle <alex@aspect.dev>
Date: Thu, 19 Dec 2024 06:34:27 +0000
Subject: [PATCH] build: point to the new material.angular.io workspace
 (#30213)

Bazel needs to be told about the nested workspace, to avoid descending into that folder.

Followup for #30208
---
 WORKSPACE | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/WORKSPACE b/WORKSPACE
index 654fc25023e8..4a699eedc643 100644
--- a/WORKSPACE
+++ b/WORKSPACE
@@ -4,6 +4,14 @@ workspace(
     managed_directories = {"@npm": ["node_modules"]},
 )
 
+# Point to the nested WORKSPACE we merged from github.com/angular/material.angular.io
+# NB: even though this isn't referenced anywhere, it's required for Bazel to know about the
+# nested workspace so that wildcard patterns like //... don't descend into it.
+local_repository(
+    name = "material_angular_io",
+    path = "./material.angular.io",
+)
+
 load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
 
 # Add NodeJS rules