Emi Matchu
8fb561338a
I don't think this actually affects any clients in practice, but now that `PetAppearance` can be influenced not just by pet state ID but also alt style ID, it's no longer correct to just use pet state ID as the `id` (the default cache key). This could theoretically cause an alt style to be locally cached as the default appearance of a species/color/pose. Instead, we now append an extra string in the case that there's also an alt style influencing the appearance. This is a bit of a mess, because I know there's some tooling that's expecting this field to be strictly the pet state ID, mainly for support/debugging purposes I think? But I imagine that's not a big deal in practice, and this change should narrow the scope of a bug like that to just be like, "error: pet state 123-with-alt-style-456 not found" when trying to save a change to it or something. Good enough! |
||
|---|---|---|
| .. | ||
| app | ||
| server | ||
| shared | ||
| react-app-env.d.ts | ||