In this changelog, we're excited to announce the release of the revamped Ruby, PHP, and Swift SDKs. We've also made a change to the TypeScript SDKs to use pnpm instead of yarn or npm. This change has improved the reliability and performance of our TypeScript SDKs.
Furthermore, we've made several improvements and fixes to the Konfig's SDKs. These include various bug fixes, better documentation, security vulnerability fixes, and more rigorous testing for PHP, Python, Ruby, Go, TypeScript, and Swift SDKs.
We revamped the Ruby, PHP, and Swift SDKs to be more consistent with the quality of our Python and TypeScript SDKs. This includes:
Improved code quality
Better test coverage
Better documentation
In particular, we removed the array of .md files that were generated as documentation and replaced it with the singular README.md file that includes everything you need to know about the SDK. Putting everything on one page makes it easier to navigate and find what you need.
Based on internal quality assurance and integration tests that we regularly run on our SDKs, we found that pnpm is a better fit for our TypeScript SDKs. It's faster, more reliable, and uses less disk space than npm or yarn. The breaking point for us was concurrency bugs that were not fixable while using yarn. When switching to pnpm, we found that these issues were resolved without special configuration. This change allowed us to fix flaky tests and continually ensure our generator was working as expected.
Improvements and Fixes
Fix lost descriptions when using
allOfwith a single schemaFix bug where TypeScript SDK would send extra data in the request body
Add
"strict": truetotsconfig.jsonin the generated TypeScript SDKFix OAuth 2.0 Token URL not being generated correctly in TypeScript SDK
Fix refreshing the token in the generated TypeScript SDK
Fix links in README.md not working on npmjs.com for the TypeScript SDK
Fix security vulnerability from
aiohttpin the generated Python SDKAdd
x-konfig-prefixsupport in Go, Ruby, PHP, Python, and TypeScriptFix default naming logic for security requirements in Go, Ruby, PHP, Python, and TypeScript
Add more rigorous testing for the PHP SDK
Add more rigorous testing for the Python SDK
Add more rigorous testing for the Ruby SDK
Add more rigorous testing for the Go SDK
Add more rigorous testing for the TypeScript SDK
Add more rigorous testing for the Swift SDK
Add
securitySchemeOverridetokonfig.yamlto override security schemesCleanup interface of top-level client class C# SDK
Fix handling of upper-case "in" field in
securitySchemesin the OpenAPI specification
No posts

Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.