Feedback by UserVoice

I suggest you ...

Expose Office API via Swagger.

OK this is a radical idea from listening to @mkristensen talk about VS.NET tooling and how they are looking at supporting Swagger 2.0 to provide code generation for RESTful APIs in VSNET.

http://devchat.tv/adventures-in-angular/019-aia-microsoft-tooling-with-mads-kristensen

I looked up Swagger and their online documentation editor, and browser and here's an example

http://petstore.swagger.wordnik.com/#!/pet/updatePet

Which is surprisingly similar to Office 365's

http://msdn.microsoft.com/en-us/library/office/dn600182(v=office.15).aspx

I think Office 365 documentation on MSDN should still be the primary resource. Any future tie in to API-Sandbox would be awesome.

But if VSNET starts to support auto-codegen (like the old days with WSDL/Soap Services) from Swagger documentation, then I can also see having Swagger documentation is extremely useful.

Again, please refer to example for the idea and the podcast about what VSNET is thinking.

46 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    John Liu shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    5 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base