From 0aba4e342a748b5051990e2b06a40251846b620d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mat=C3=ADas=20Hern=C3=A1ndez?= <matiashe@google.com>
Date: Wed, 8 Mar 2023 12:43:06 +0100
Subject: [PATCH] Fix failing checkcolor_hook in Settings

(Fixed according to the instructions in prebuilts/checkcolor/README.md).

Fixes: 272244692
Test: repo upload
Change-Id: Ib53c6b302984250e6c4dfe058a74697a62b94e26
---
 color-check-baseline.xml | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/color-check-baseline.xml b/color-check-baseline.xml
index 3ba943b8e90..911a95b5001 100644
--- a/color-check-baseline.xml
+++ b/color-check-baseline.xml
@@ -4477,6 +4477,22 @@
             column="13"/>
     </issue>
 
+    <issue
+        id="HardCodedColor"
+        severity="Error"
+        message="Avoid using hardcoded color"
+        category="Correctness"
+        priority="4"
+        summary="Using hardcoded color"
+        explanation="Hardcoded color values are bad because theme changes cannot be uniformly applied.Instead use the theme specific colors such as `?android:attr/textColorPrimary` in attributes.&#xA;This ensures that a theme change from a light to a dark theme can be uniformlyapplied across the app."
+        errorLine1="            android:tint=&quot;#4F8438&quot;"
+        errorLine2="            ~~~~~~~~~~~~~~~~~~~~~~">
+        <location
+            file="res/layout/locale_dialog.xml"
+            line="36"
+            column="13"/>
+    </issue>
+
     <issue
         id="HardCodedColor"
         severity="Error"