Espial VS swagger-petstore

Tangentially, I would recommend exporting your Pinboard collection periodically to somewhere safe. The service has gotten sketchy in the last year or two. I transitioned mine to a self-hosted instance of Espial.

An alternative, one that I began using a year ago after losing confidence in Pinboard is the self-hosted Espial - https://github.com/jonschoning/espial.

The visual presentation is a near complete clone of Pinboard. It also provides a route for Pinboard import.

Link repository - I use a self-hosted instance of Espial, but again the technology is unimportant. I mention this only because one of the philosophies of the Zettelkasten is to avoid the collector's fallacy where just by saving something you think you know it. So links go here if I might want to find it again in the future but I don't have time to think about it now or take notes on it into the ZK.

Saving URL's: For the most part, I don't like existing built-in bookmarking solutions in most browsers, because they seem to treat metadata cursorily or just ignore it. I've started using Espial which is a self-hosted Pinboard knock-off that allows me to tag and comment on URL's that I save.

you could run my self-hosted bookmarking site locally (which includes basic notes) https://github.com/jonschoning/espial

I actively avoid super general code in my Haskell applications.

Here's some code to add a bookmark in an api controller:

https://github.com/jonschoning/espial/blob/master/src/Handle...

Swagger offers more than just a user-friendly interface for exploring APIs. It also provides multiple generators that can produce code typically written by hand. As an Angular developer, this blog post will focus on the typescript-angular generator.

Failed to create a client for Java. The generator imports Java's types instead of TeamCity's. There are bugs described for the Java client in both the Swagger generator and the OpenAPI generator. Let's see how the generator behaves when building a Kotlin client.

[swagger-codegen](https://github.com/swagger-api/swagger-codegen) generates code from an OpenAPI definition, and it supports Rust code output (client and/or server).

Swagger contains three greats tools to work with the specification: Swagger UI, Swagger Editor and Swagger Codegen. The Swagger UI renders OpenAPI specs as interactive API documentation, Swagger Editor is a browser-based editor where you can write OpenAPI specs and Swagger Codegen generates server stubs and client libraries from an OpenAPI spec like the OpenAPI generator.

We ran into some minor issues (#1201, #1210, #1355, #1356 and #1769) and fixed some stuff we stumbled upon along the way, although it didn't really bother us as well (#1451 and #1769).

I am interested in integrating a swagger-codegen generated Python server with an existing Flask application. swagger-codegen generates a Python implementation based on the Connexion library from a Swagger API specification.

The method takes a query, String, and a completion block, (Result<[String], Error>) -> Void, which is triggered once the request finishes. Its internal implementation doesn't really matter since it could be from an external framework or generated by a code generator from the API specification.

The Java codegen options are here: https://github.com/swagger-api/swagger-codegen/issues/7795 (believe it or not).

Creating TS types/interfaces manually can be tedious. But, if you have JSON responses of your APIs, you can quickly convert those JSON responses to TS interfaces using VS Code extension Paste JSON as Code. Also, if your backend already uses Swagger for API, you can auto-generate all the TS types of your API models using swagger-codegen