Matchu e7cc20876b use xmlrpc to load pets, not json.php ... The AMFPHP gateway's json.php endpoint has always had a problem parsing pets whose names start with digits… I've dug into it before, and checked again today, and there really is just no way around it: d584b58e95/core/json/app/Actions.php (L43) And there aren't any reliable AMFPHP Node libraries out there to make the actual native AMF call. Buuuut! In today's investigation, I noticed the xmlrpc.php endpoint for the first time. And, wouldn't you know it, there's //great// reliability for something as enterprise-standard as that! So here, I've switched over to using an xmlrpc client library, which simplifies our calling code //and// makes number pets work correctly 😁 I wouldn't have done it just for the simplification, I think bringing in a library is net more complexity… but getting this finally right is a big relief.		2020-10-22 23:22:04 -07:00
..
__snapshots__	simplify validPetPoses out of the server directory	2020-09-06 00:40:00 -07:00
lib	remove detailed gql from honeycomb traces	2020-09-19 21:34:35 -07:00
query-tests	mutations to mark an item as owned/wanted	2020-10-22 20:35:06 -07:00
types	use xmlrpc to load pets, not json.php	2020-10-22 23:22:04 -07:00
auth.js	extract server auth into auth.js	2020-10-22 19:53:10 -07:00
db.js	enable running against a local dev database	2020-10-06 06:18:19 -07:00
index.js	extract server auth into auth.js	2020-10-22 19:53:10 -07:00
loaders.js	refactor Outfit.js to split Pet to a separate type	2020-09-27 03:18:46 -07:00
modeling.js	disable new modeling code, until some future day	2020-10-07 07:49:27 -07:00
util.js	update labeled field for pet appearances	2020-10-03 04:05:25 -07:00
util.test.js	add snapshot tests for loadBodyName	2020-08-21 16:22:16 -07:00