Skip to main content

15 posts tagged with "Konfig"

View All Tags

· 2 min read

We are excited to announce the launch of our newest product at Konfig!

Introducing: API Reference

The Problem

The next step after generating SDKs is adding them to your docs. But as soon as you do, something feels off. Your API reference is not integrated with your SDKs and you have to maintain two separate pages. You manually copy-paste code snippets from your SDKs to your docs and you have to update them every time your API changes. So we created a better way.

The Solution

Introducing API Reference by Konfig. It's a single page that combines your API reference and SDKs. It's automatically generated from your OpenAPI spec and SDKs. It's always up-to-date and it's always in sync with your API. It allows you to dynamically generate code snippets for your SDKs and make API requests directly from your docs. It's a single source of truth for your API.

Portal
Live API Reference Page for SnapTrade

Currently, we are deploying with a few early customers. If you are interested in trying it out, please reach out to dylan@konfigthis.com.

Improvements and Fixes
  • Allow for configuration of a specific operation in SDK README.md files
  • Remove quotes from strings when copying in demo portal
  • Added "konfig versions" command to CLI to query currently published SDKs
  • Add a one-time deprecation warning for deprecated operations in Python SDK

· 3 min read

Last week we merged our plugin into Backstage (Pull Request) to generate SDKs for internal services. For those that love to follow and discuss technology, we also published a blog post where Dylan reviewed 1,000s of GraphQL vs. REST perspectives. We also made a lot of improvements to our Python, TypeScript, and PHP SDK generators.

Backstage Plugin

SDKs help onboard external developers but we know that the same problem exists inside organizations when integrating APIs from different teams owning different services. Backstage is a developer portal for centralizing your infrastructure and enabling product teams to quickly ship high-quality code. So we created a Backstage plugin to auto-generate SDKs for internal API services. If you are interested in generating SDKs for your internal APIs please reach out to us and we would love to talk. Check out our official plugin here!

Backstage Plugin
Backstage Plugin Marketplace with our official SDK generation plugin

Blog Post: I Reviewed 1,000s of GraphQL vs. REST Perspectives

Ask any developer: do you prefer GraphQL or REST? This often leads to opinionated conversations, sometimes even devolving into vulgar opinions rather than objective facts. To delve into the GraphQL vs. REST debate, I scoured platforms where developers frequently discuss such matters: YouTube, Reddit, Twitter, and Hacker News. I parsed 1,000s of discussions and synthesized my findings in this blog post, striving to present only thought-provoking perspectives. Read more here!

GraphQL vs. REST Blog Post
I reviewed 1,000s of GraphQL vs. REST Perspectives in our latest blog post Improvements and Fixes (there are lots of them this past two weeks!)
Improvements and Fixes
  • Konfig CLI now gives a warning to update to the latest version
  • Added "changeset" command for Konfig CLI to automate SDK generation using GitHub actions
  • When running "konfig generate", if "specInputPath" is set then "konfig fix" is also executed
  • Fix generated documentation referring to non-existent response variable in Python SDK
  • Konfig CLI now always runs a mock server when running "konfig test"
  • Custom package.json scripts can be added to TypeScript SDK using konfig.yaml
  • Fix bug in Python SDK where unexpected keyword argument error is thrown when attaching extra properties to request bodies inside a customized SDK
  • Add label to top-level README to differentiate SDKs that have PHP 7+ or PHP 8+ support (see SDK table in example README)
  • Reference OpenAPI "tag" instead of "class" inside operation table in generated TypeScript SDK README
  • Add flag "useDescriptionInOperationTableDocumentation" to konfig.yaml for TypeScript SDK to use "description" instead of "summary" field from operation in generated operation table for README.md
  • Fix "ReadableStream" not defined in TypeScript SDK when API error is encountered in Node.js
  • Improve PHP 7+ support option
  • Error is now thrown if "topLevelOperations" references an operation ID that does not exist in the OAS
  • Fix bug where required path parameter causes syntax issue in Python SDK
  • Fix bug where dictionaries in generated Python SDK documentation was using "=" instead of ":" for dict values
  • Add "konfig published" command for listing all currently published SDKs
  • Add "konfig lint-python" command to run Ruff linter on Python SDK
  • Fix bug in Python SDK where "_headers" is undefined
  • Handle generators listed under "additionalGenerators" when using "konfig bump"

· 3 min read

At Konfig, we are rapidly making progress towards building the easiest way to onboard developers to your API. To keep our followers up-to-date, we are starting this newsletter that will feature 2-3 of our biggest product updates and little fixes.

STATISTICS.md

Now konfig generate will generate a file named STATISTICS.md that contains a count for Lines of Code in each SDK for your API. Here is an example that we generated. This file is generated in the same directory as your konfig.yaml file. In the future, we would also like to add more data such as weekly downloads.

STATISTICS.md

_11
# SDK Statistics
_11
_11
| SDK Name | Lines of Code |
_11
|------------|---------------|
_11
| java | 89900 |
_11
| ruby | 47516 |
_11
| python | 104319 |
_11
| typescript | 18063 |
_11
| csharp | 58322 |
_11
| php | 99705 |
_11
| **Total** | 417825 |

Interactive Tutorial

Our interactive tutorial is now live! Learn how to generate SDKs with a guided interface. This is a great way to get started with Konfig if you would like to generate SDKs yourself.

Interactive Tutorial

Improved TypeScript SDK Error

Instead of just throwing the error from the underlying request library, axios, we now generate a file called error.ts that contains a custom Error class. The name of the class is based off the client name in your konfig.yaml file. The new custom error message has a cleaner interface and better inline documentation. In a Next.js API environment, the logged errors now exclude a lot of the garbage that was not helpful when debugging.

error.ts

_36
/**
_36
* This class provides a wrapper for network errors when making requests to OpenAPI Petstore
_36
*/
_36
export class AcmeError extends Error {
_36
/**
_36
* The response body
_36
*/
_36
readonly responseBody: unknown;
_36
_36
/**
_36
* The error code provided from the underlying "axios" library which can be
_36
* more descriptive than the HTTP status descriptions.
_36
*/
_36
readonly code?: string;
_36
_36
/**
_36
* The status code from the response.
_36
* For explanations, refer to https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
_36
*/
_36
readonly status?: number;
_36
_36
/**
_36
* The status text from the response.
_36
* For explanations, refer to https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
_36
*/
_36
readonly statusText?: string;
_36
_36
/**
_36
* The URL that the original request was sent to
_36
*/
_36
readonly url?: string;
_36
_36
/**
_36
* HTTP request method (see https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods)
_36
*/
_36
readonly method?: string;

Improvements and Fixes
  • Support for GitLab publishing in Java SDK
  • Streaming support in TypeScript SDK for Node.js environments
  • Improved class hierarchy in TypeScript SDK to allow for custom classes to call generated methods
  • Improved class hierarchy in Java SDK to allow for custom classes to call generated methods
  • Fixed bug in Python SDK when circular dependency was present in OpenAPI spec