Fix eslint no-unescaped-entities errors

equinor · Jan 17, 2025 · 87eb838 · 87eb838
1 parent d4b373e
commit 87eb838
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/frontend/eslint.config.js b/frontend/eslint.config.js
@@ -14,7 +14,6 @@ export default [
   {
     rules: {
       "react/react-in-jsx-scope": "off",
-      "react/no-unescaped-entities": "off",
       "react/display-name": "off",
       "@typescript-eslint/no-explicit-any": "off",
     }

diff --git a/frontend/src/components/Alerts/FailedMissionAlert.tsx b/frontend/src/components/Alerts/FailedMissionAlert.tsx
@@ -33,8 +33,8 @@ const FailedMission = ({ missions }: MissionsProps) => {
 
     return (
         <StyledButton onClick={goToMission} variant="ghost" color="secondary">
-            <strong>'{mission.name}'</strong> {TranslateText('failed on robot')}{' '}
-            <strong>'{mission.robot.name}':</strong> {mission.statusReason}
+            <strong>{`'${mission.name}'`}</strong> {TranslateText('failed on robot')}{' '}
+            <strong>{`'${mission.robot.name}'`}:</strong> {mission.statusReason}
         </StyledButton>
     )
 }