From 1263b9cc42a8f4f7c1f383966c6843e3aca69a86 Mon Sep 17 00:00:00 2001
From: Stephen Cprek <steve.cprek@favordelivery.com>
Date: Fri, 17 Feb 2023 16:33:07 -0500
Subject: [PATCH] Add ADR type to search page and result cast

Signed-off-by: Stephen Cprek <steve.cprek@favordelivery.com>
---
 plugins/adr/README.md | 20 ++++++++++++++++++--
 1 file changed, 18 insertions(+), 2 deletions(-)

diff --git a/plugins/adr/README.md b/plugins/adr/README.md
index a669762dad..4860406229 100644
--- a/plugins/adr/README.md
+++ b/plugins/adr/README.md
@@ -71,16 +71,32 @@ Afterwards, add the following code snippet to use `AdrSearchResultListItem` when
 import { AdrSearchResultListItem } from '@backstage/plugin-adr';
 
 ...
+<SearchType.Accordion
+  name="Result Type"
+  defaultValue="software-catalog"
+  types={[
+    ...
+    {
+      value: 'adrs',
+      name: 'Architecture Decision Records',
+      icon: <DocsIcon />,
+    },
+  ]}
+/>
 
-case 'adr':
+...
+
+case 'adrs':
   return (
     <AdrSearchResultListItem
       key={document.location}
-      result={document}
+      result={document as AdrDocument}
     />
   );
 ```
 
+> Note the `AdrDocument` might not be needed in newer versions https://github.com/backstage/backstage/issues/13723
+
 ## Custom ADR formats
 
 By default, this plugin will parse ADRs according to the format specified by the [Markdown Architecture Decision Record (MADR) v2.x template](https://github.com/adr/madr/tree/2.1.2). If your ADRs are written using a different format, you can apply the following customizations to correctly identify and parse your documents: