It can be somewhat irritating having to navigate the vendor lists for specific items, so it would be nice if items could also link back to a vendor (hash) that the item can be purchased from, possibly along with the cost.
You might add this to #756 as well!
Hmm, I could see giving a set of vendor hashes + vendor item indexes, but what I'd be hesitant about would be any implication that the given vendor item index would actually be sold, and at what price.
The price can potentially be modified at runtime, and I have no guarantee until we actually query for Vendors via live data calls that any given item will be sold at any given price.
But if such a denormalization of the data would be useful for folks, I would consider adding the lookups at least!
$0.02 - Sale status/value aside, I do think a simple trace back to a vendor (or multiple vendors/sources?) would be valuable. Given the work that has been done by some folks to build these indexes manually, I have to imagine that having that optional data on each item itself could save a lot of client-side processing, especially for lookup-style services that mainly focus on that relational information. 馃
TFS 746595
Will be in the January release!
This should be fixed as of today's deployment (1/29)!
Most helpful comment
Will be in the January release!