#contributions

Implementing OpenAPI Spec in Go Client

TLDR Kishore Nallan suggested using the openapi spec for generating classes/structs for the Go client, making it easier for statically typed languages. The spec must be updated for the recent changes.

33mo

Join the chat

May 04, 2021 (33 months ago)

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

03:55 PM

For generating the classes / structs for the client, we can use the openapi spec that the Go client is using here: https://github.com/typesense/typesense-go/blob/master/typesense/api/openapi.yml

This way we don't have to generate those classes by hand. Thoughts?

03:56

Kishore Nallan

03:56 PM

This is up-to-date till v0.19 -- we need to update it for the changes in 0.20 and we should be ready to go.

03:57

Kishore Nallan

03:57 PM

The python / ruby clients don't use specific classes since the languages are not statically typed. But for statically typed languages, this is a much easier and scalable approach.

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Discussing the Functionality and Structure of Typesense Client Libraries

Jason explained how Typesense client libraries function and their architecture. Jason and Masahiro guide Joe in his work on the Java client, emphasizing a consistent method call structure across different languages. Joe highlights his progress and difficulties.

33mo

Using Typesense from Rust

martian sought advice on using Typesense from Rust. Kishore Nallan directed to a community-led Rust client and confirmed that a Rust client could be generated using the openapi spec.

28mo

Request for API Update and Go SDK Release

adil reported an issue and requested an API spec update. Jason asked for a PR and acknowledged completion. adil inquired about SDK updates, specifically Go. Kishore Nallan released the updated version.

17mo