These are chat archives for arenanet/api-cdi
That forum post reminded me, @lye :point_up: 17 januari 2018 07:39
Lye, speaking of permissions, you were probably (half-)joking anyway, but did you see our suggestion a while back about that we can probably offer to help with tagging issues on the repo? Most likely just tagging by endpoint or something, but at least it makes it easier to navigate.
Also, this reminds me of another thing ANet did a while back on the forums, where certain community members were representatives (or something) of various parts of the forum, helped others out and filter things for developers iirc. Maybe something like that can work in some way for the API too? The API part on the forums isn't that highly active, but it might help if the responsibility is shifted towards various development teams.
This is something I’ve looked into previously, and it’s unfortunately not technically feasible to expose via the API. The problem basically boils down to two big issues:
- It’s not possible to determine which vendors are player-accessible. There are some test vendors that you’ll never see which sell things for fairly cheap prices, and no good way to tell them apart from player-accessible vendors.
- Vendor prices are per-vendor, not per-item: different vendors may have different prices for the same item. An example of this are the Dry Top vendors, whose wares are sold for a conditional amount.
/v2/vendors [l,d]is a thing, i guess we can only guess
throw new Exception('not implemented')though)
needs deploytag on github, which usually means the implementation is done