From 67539877a93ab6178a4a7ba87b94a133733a4fe1 Mon Sep 17 00:00:00 2001
From: Nicolas Guichard <nicolas.guichard@kdab.com>
Date: Mon, 27 Nov 2023 20:03:10 +0000
Subject: [PATCH] Bug 1490144 - Mozsearch indexer: remove pretty field from
 super/override relationships. r=asuth

This is the update from https://github.com/mozsearch/mozsearch/pull/672.
Mozsearch doesn't expect the pretty field on super/override
relationships anymore. It doesn't hurt being there, but let's clean it
up anyway.

Differential Revision: https://phabricator.services.mozilla.com/D194524
---
 build/clang-plugin/mozsearch-plugin/MozsearchIndexer.cpp | 2 --
 1 file changed, 2 deletions(-)

diff --git a/build/clang-plugin/mozsearch-plugin/MozsearchIndexer.cpp b/build/clang-plugin/mozsearch-plugin/MozsearchIndexer.cpp
index 1866c9438593..dca757511bb7 100644
--- a/build/clang-plugin/mozsearch-plugin/MozsearchIndexer.cpp
+++ b/build/clang-plugin/mozsearch-plugin/MozsearchIndexer.cpp
@@ -1064,7 +1064,6 @@ public:
 
         J.objectBegin();
 
-        J.attribute("pretty", getQualifiedName(BaseDecl));
         J.attribute("sym", getMangledName(CurMangleContext, BaseDecl));
 
         J.attributeBegin("props");
@@ -1219,7 +1218,6 @@ public:
         // I think our pre-emptive dereferencing/avoidance of templates may
         // protect us from this, but it needs more investigation.
 
-        J.attribute("pretty", getQualifiedName(MethodDecl));
         J.attribute("sym", getMangledName(CurMangleContext, MethodDecl));
 
         J.objectEnd();