Oops, fix SVG message and build error
Ah hm, not sure why this only showed up once I tried a prod deploy, but I declared `hiResMode` twice in there, because we already had fixed this bug for item layers but not pet layers! In this change, I fix the duplicate `hiResMode` declaration, and update the new pet layers message to match the item layers message.
This commit is contained in:
parent
3642e4c32a
commit
7c3298d5b2
1 changed files with 3 additions and 4 deletions
|
@ -103,7 +103,6 @@ function OutfitKnownGlitchesBadge({ appearance }) {
|
||||||
|
|
||||||
// Look for items with the OFFICIAL_SVG_IS_INCORRECT glitch. Only show this
|
// Look for items with the OFFICIAL_SVG_IS_INCORRECT glitch. Only show this
|
||||||
// if hi-res mode is on, because otherwise it doesn't affect the user anyway!
|
// if hi-res mode is on, because otherwise it doesn't affect the user anyway!
|
||||||
const [hiResMode] = useLocalStorage("DTIHiResMode", false);
|
|
||||||
if (hiResMode) {
|
if (hiResMode) {
|
||||||
for (const item of items) {
|
for (const item of items) {
|
||||||
const itemHasOfficialSvgIsIncorrect = item.appearance.layers.some((l) =>
|
const itemHasOfficialSvgIsIncorrect = item.appearance.layers.some((l) =>
|
||||||
|
@ -246,9 +245,9 @@ function OutfitKnownGlitchesBadge({ appearance }) {
|
||||||
glitchMessages.push(
|
glitchMessages.push(
|
||||||
<Box key={`official-svg-is-incorrect-for-pet-layer-${layer.id}`}>
|
<Box key={`official-svg-is-incorrect-for-pet-layer-${layer.id}`}>
|
||||||
There's a glitch in the art for this pet's <i>{layer.zone.label}</i>{" "}
|
There's a glitch in the art for this pet's <i>{layer.zone.label}</i>{" "}
|
||||||
zone that prevents us from showing the full-scale SVG version of the
|
zone that prevents us from showing the SVG image for Hi-Res Mode.
|
||||||
image. Instead, we're showing a PNG, which might look a bit blurry
|
Instead, we're showing a PNG, which might look a bit blurry on
|
||||||
on larger screens.
|
larger screens.
|
||||||
</Box>
|
</Box>
|
||||||
);
|
);
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue