TFS2017/2018 docs about vsts-rest-api-specs

[huntantr]

The version mapping I had, but that doesn't help with the new documentation, as I don't know what was available in those versions, now everything shows 4.1. I am currently running TFS2017.2 so I need to be able to see what api's are available in 3.2.
Just like on the other documentation that has filtering based on whether it is VSTS, TFS2018, TFS2017, etc, the api's documentation requires this as well so that we can correctly see what is available to use. Being able to only see the latest for a version we are not even able to use is not helpful.
I am right in the middle of designing a customization and can't as I don't know what's available at my version.

[wnjenkin]

We've renamed the folder for these docs. Here is the new link https://docs.microsoft.com/en-us/vsts/integrate/previous-apis/overview?view=vsts

[wnjenkin]

Thanks for your feedback. I've provided a version mapping which should help distinguish between version number. Unfortunately there isn't a way for us to show which apis are supported on TFS. This is something we certainly need to add. I'm adding an enhancement tag and leaving this issue open until we can resolve.

Version mapping
3.0 - 2017 RTM
3.1 - 2017 update 1
3.2 - 2017 update 2
4.0 - 2018
4.1 - 2018 update 2

[japj]

Perhaps going back in history and create a seperate branch per api version?
Or do you want to keep a single source tree with all api versions in it?

[huntantr]

The issue seems to be being handled in other parts of the documentation. I would recommend something like what is being down with powershell: https://docs.microsoft.com/en-us/powershell/scripting/powershell-scripting?view=powershell-6. Providing a filter for the API version would be extremely useful.

[wnjenkin]

Our older apis are now available on our docs site. They can be found here https://docs.microsoft.com/en-us/vsts/integrate/legacy-apis/overview?view=vsts. This should hopefully unblock your development.

[huntantr]

Why would you put this under Legacy? This is still valid information and should all be in the same location. Going forward how are the different versions of api's going to be handled? I hope that filtering will be applied to the standard location as well as v4.2, v5.0, v5.1, etc. comes out.
Ideally it would be best if the filtering applied to the api's was based on their version.

[wnjenkin]

Ideally yes, these documents would appear in the same section but it's not as easy for us to do this right now. To unblock development ASAP, we've decided to port over a copy of our old documentation site. Going forward, we will have a version selector which allows you to toggle between different api versions and it will be applied to our standard location.

[huntantr]

That works for me. Thank you. I look forward to the final update to the docs.