dice/impress
1
0
Fork 0
forked from OpenNeo/impress
Code Pull requests Activity
impress/src/server/query-tests/__snapshots__/Species.test.js.snap

284 lines
5.1 KiB
Text
Raw Normal View History

split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
// Jest Snapshot v1, https://goo.gl/fbAQLP
exports[`Species loads all species 1`] = `
Object {
"allSpecies": Array [
Object {
"id": "1",
"name": "Acara",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "93",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "2",
"name": "Aisha",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "106",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "3",
"name": "Blumaroo",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "47",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "4",
"name": "Bori",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "84",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "5",
"name": "Bruce",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "146",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "6",
"name": "Buzz",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "250",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "7",
"name": "Chia",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "212",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "8",
"name": "Chomby",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "74",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "9",
"name": "Cybunny",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "94",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "10",
"name": "Draik",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "132",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "11",
"name": "Elephante",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "56",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "12",
"name": "Eyrie",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "90",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "13",
"name": "Flotsam",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "136",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "14",
"name": "Gelert",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "138",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "15",
"name": "Gnorbu",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "166",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "16",
"name": "Grarrl",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "119",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "17",
"name": "Grundo",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "126",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "18",
"name": "Hissi",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "67",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "19",
"name": "Ixi",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "163",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "20",
"name": "Jetsam",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "147",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "21",
"name": "Jubjub",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "80",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "22",
"name": "Kacheek",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "117",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "23",
"name": "Kau",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "201",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "24",
"name": "Kiko",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "51",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "25",
"name": "Koi",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "208",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "26",
"name": "Korbat",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "196",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "27",
"name": "Kougra",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "143",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "28",
"name": "Krawk",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "150",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "29",
"name": "Kyrii",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "175",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "30",
"name": "Lenny",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "173",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "31",
"name": "Lupe",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "199",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "32",
"name": "Lutari",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "52",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "33",
"name": "Meerca",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "109",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "34",
"name": "Moehog",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "134",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "35",
"name": "Mynci",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "95",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "36",
"name": "Nimmo",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "96",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "37",
"name": "Ogrin",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "154",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "38",
"name": "Peophin",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "55",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "39",
"name": "Poogle",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "76",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "40",
"name": "Pteri",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "156",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "41",
"name": "Quiggle",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "78",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "42",
"name": "Ruki",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "191",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "43",
"name": "Scorchio",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "187",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "44",
"name": "Shoyru",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "46",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "45",
"name": "Skeith",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "178",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "46",
"name": "Techo",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "100",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "47",
"name": "Tonu",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "130",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "48",
"name": "Tuskaninny",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "188",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "49",
"name": "Uni",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "257",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "50",
"name": "Usul",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "206",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "51",
"name": "Wocky",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "101",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "52",
"name": "Xweetok",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "68",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "53",
"name": "Yurble",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "182",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "54",
"name": "Zafara",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "180",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
Object {
"id": "55",
"name": "Vandagyre",
cache item data when switching standard colors Previously, when changing a pet's color, we would refresh the items panel and send a new network request for the item appearances, even though they're all the same. This is because item appearance data is queried by species/color, for ease of specification. But! Item appearances are //cached// by body ID. So, if this is a standard color, it's not hard to look in the cache for the standard color's body ID! Now, most color changes are faster and don't flicker the item panel anymore. We do still refresh the panel and send the requests for color changes that _do_ matter though, like standard <-> mutant!
2020-08-31 18:25:42 -07:00
"standardBodyId": "306",
split query tests into separately runnable files!
2020-04-25 23:03:58 -07:00
},
],
}
`;
Copy permalink