fix: Use translations for content types in search results

whitespace-se · Jul 20, 2023 · 26ef53c · 26ef53c
1 parent bef272f
commit 26ef53c
Showing 1 changed file with 10 additions and 3 deletions.
diff --git a/packages/gatsby-plugin-search/src/components/search-hits/DefaultSearchHit.js b/packages/gatsby-plugin-search/src/components/search-hits/DefaultSearchHit.js
@@ -3,6 +3,7 @@ import { useContentType } from "@whitespace/gatsby-theme-wordpress-basic/src/hoo
 import { memoize } from "lodash-es";
 import PropTypes from "prop-types";
 import React from "react";
+import { useTranslation } from "react-i18next";
 
 import DeprecatedSearchHit from "../SearchHit";
 import SearchTeaser from "../SearchTeaser";
@@ -34,6 +35,7 @@ export default function DefaultSearchHit({
   hit,
   ...restProps
 }) {
+  const { t } = useTranslation();
   const contentType = useContentType(hit.contentType);
 
   if (DeprecatedSearchHit) {
@@ -52,15 +54,20 @@ export default function DefaultSearchHit({
     // taxonomies,
   } = hit;
 
+  let contentTypeName = t(
+    [`contentTypes.${contentType.name}.name`, contentType.labels?.singularName],
+    {
+      count: 1,
+    },
+  );
+
   return (
     <SearchTeaser as="li" {...restProps}>
       <SearchTeaserContent>
         <SearchTeaserTitle link={{ url }}>{label}</SearchTeaserTitle>
         {text && <SearchTeaserExcerpt>{text}</SearchTeaserExcerpt>}
         <SearchTeaserMeta>
-          {contentType?.labels?.name && (
-            <span>{contentType.labels.singularName}</span>
-          )}
+          {!!contentTypeName && <span>{contentTypeName}</span>}
           {date && <Time date={date} format={dateFormat} />}
         </SearchTeaserMeta>
       </SearchTeaserContent>