From 84b623645e306f0dbd64dd213b53b4d1fc7f3b17 Mon Sep 17 00:00:00 2001
From: Harsha Teja Kanna <h7kanna@gmail.com>
Date: Wed, 23 Oct 2024 09:53:35 -0400
Subject: [PATCH] Fixed custom element sanitizer config to be optional in types

Signed-off-by: Harsha Teja Kanna <h7kanna@gmail.com>
---
 plugins/techdocs/config.d.ts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/plugins/techdocs/config.d.ts b/plugins/techdocs/config.d.ts
index 6103f273b5..bfc98a7927 100644
--- a/plugins/techdocs/config.d.ts
+++ b/plugins/techdocs/config.d.ts
@@ -49,7 +49,7 @@ export interface Config {
        *  this will allow all custom elements with tag name matching `^backstage-` like <backstage-custom-element /> etc.
        * @visibility frontend
        */
-      allowedCustomElementTagNameRegExp: string;
+      allowedCustomElementTagNameRegExp?: string;
       /**
        * Allows listed custom element attribute name regex
        * Example:
@@ -57,7 +57,7 @@ export interface Config {
        *  this will allow all custom element attributes matching `attribute1` or `attribute2` like <backstage-custom-element attribute1="yes" attribute2/>
        * @visibility frontend
        */
-      allowedCustomElementAttributeNameRegExp: string;
+      allowedCustomElementAttributeNameRegExp?: string;
     };
   };
 }