These are chat archives for arenanet/api-cdi
/v2/items/is changing between builds due to whitelisting, no?
/v2/buildis incremented you have to invalidate your entire cache if you want to pick up minor changes
I wanted to check in as well and give you all a bit of insight into what's going on with the APIs right now. Our first priority is triage; as Ylan mentioned, the two of us will directly be watching GitHub and this forum for reports and feedback on what's most important to you. Once we have established some general ordering for what will be tackled, we're working on finding multiple folks from the GW2 engineering team who can contribute to keeping the APIs up to date and solid. As several people have identified already, having the entire API project tasked to one person is suboptimal in a lot of ways. So we want to address that specifically going forward.
I'm sure you all can appreciate how huge a game like GW2 is and how much effort goes into keeping it living and fresh; so hopefully it isn't a surprise when I say that we have a lot going on and a lot of competing demands on the team's time and attention. While the APIs are something we are very much interested in maintaining and supporting for the future, we do appreciate your understanding that sometimes other things are higher priorities, and so we are trying very hard not to promise things right now. That said, as things do solidify and become clearer, we will definitely be keeping the community up to date.
One loosely related thing I would love some community feedback on - how do you all feel about GitHub and specifically how we've been using it up until now? Is there anything that you would like to see changed in terms of how we collect API requests and track the associated development work?
/v2/build, if that is a new number you can delete your cache. You also always have to query
/v2/itemsfor a list of IDs due to new items getting whitelisted. You can however cache responses for particular items between builds. Is that right @lye?