Closed carloslbello closed 1 year ago
I suspected it could end up being an issue with marketplace SKUs. I don't see a good way around this but to use an i32.
I've changed the integer type to i32 in https://github.com/juliarose/backpacktf-api/commit/ad68f3d77eef49039cfce40ef1e69ad49f512de1
Marketplace.tf allows listing a variety of craft hats to be listed as 'Random Craft Hat', an item that does not actually exist but that has an SKU of
-100;6
(see here). When cross-listed to Backpack.tf the defindex remains as -100 and currently the code for listing snapshots (and probably for listings from the websocket) can't handle it without returning an error.I think it may be potentially helpful to silently discard these listings, or create a way for the user to opt to handle them in another specific way. Deducing the correct defindex may not always be possible, especially without a copy of the item schema, and (for example) I am not interested in Marketplace.tf cross listings anyway.
Snapshot example:
Error example: