If I don’t want to lose context, I must download the YAML, open it in the editor and quickly find myself out of sync with any changes my fellow devs had made. But that’s always been a tedious affair in the past. You see, being a front-end developer on SwaggerHub who consumes SwaggerHub APIs, my natural inclination is to read, use, and work with those APIs in VS Code. That’s all preamble to the core conceit of this blog: VS Code and SwaggerHub. ![]() If I’m unsure about something, I can poke around at the open source innards and see what’s making things tick. It’s fast, it’s neat, and as a JavaScript developer, it’s also very handy that it’s written in JavaScript. Now as a front-end developer, my IDE of choice is Visual Studio Code. ![]() They’re everywhere! We use them ourselves to write the application that documents the very APIs we’re using! I’m a front-end developer for SwaggerHub, and this means my exposure to APIs comes primarily as a consumer – I help sculpt the result of our APIs by being a first-party user. One of the best things about working with SwaggerHub is the exposure to APIs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |