Retrofit VS SQLDelight

from this point on, I will assume, you have a basic understanding of Retrofit. To get the most out of this tutorial I would actually suggest you have a retrofit client already implemented in your application.

Now you might think that in order to make the request we are going to use Retrofit but in reality we are going to be sending out an implicit intent like so:

This particular blog post will be us building on the information from the previous blog post and using the authorization code from the GitHub OAuth API in combination with Retrofit. To finally get a access token, which allows us to make requests to the API on a behalf of a user.

Hey HN!

If you're a fan of Swift you may have noticed that with WWDC 2023 came the (beta) release of macros. They're super powerful and expressive!

I've been wishing Swift had a [Retrofit](https://square.github.io/retrofit/) style API definition library for years, and with macros it seemed like this was now possible.

I'd like to show you all Papyrus, a library that turns your APIs into type-safe Swift protocols.

Would love to get your feedback.

https://github.com/joshuawright11/papyrus

When it comes to consuming APIs I can definitely recommend Retrofit. Hopefully that's enough to get you started on where to look!

For Android you should use a more mobile friendly framework like Retrofit or if you use Kotlin you can use the multi-platform Ktor library with it's client module

for example https://square.github.io/retrofit/ have mentioned it in at the bottom. Similarly there maybe other rules for other dependencies. Usually I search the missing classes error in google and find some proguard rule for it.

Retrofit in combination with OkHttp for fetching data from server (which hopefully already exists)

The first get request is to retrieve a list of objects and the second one is to get a single one. You can read more about RetroFit here.

So I've been playing around with search.maven.org and perhaps I'm not quite understanding it. For example, if I look for Retrofit I'm not seeing anything that resembles retrofit above https://central.sonatype.dev/search?q=Retrofit.

This seems to be similar to https://github.com/cashapp/sqldelight, and I've always wanted a python equivalent!

In typescript, there are query builders (not talking about ORMs) that can basically do this within the type system, but that would be infeasible in python's type system. This approach (type/code generation is a good alternative, though I like using sqlalchemy / alembic to manage schemas/migrations.

One thing I'm curious about is how it knows the types of columns? I looked quickly at the Readme but didn't see it (probably a parameter somewhere I missed).

That functionality has existed for almost exactly a year

- SQLDelight - great experience overall, the only issue that I found, was when that I made a database migration that worked on Android, but not on iOS (https://github.com/cashapp/sqldelight/issues/3812)

Database - SQLDelight

room is a great example but like I said our data is kotlin-only so we tend to use libraries like sqlDelight.

This seems similar to https://cashapp.github.io/sqldelight/ for kotlin, I think this approach is pretty neat, good luck with it!

Sounds like you want what SQLDelite offers, but for TypeScript. SQLDelite is only for Kotlin and SQLite though.

SQLDelight had neat built in support for this

https://cashapp.github.io/sqldelight/

You would really like sqldelight[1] then. It takes the concept of an ORM and flips it on its head. Instead of mapping function calls to SQL statements, it lets you write SQL statements and then generates classes for you that have methods for those statements.

For instance, you could have a SQL statement like getCardsForFight: select * from fights where cardId = ? and titleFight = ?, and it would generate a class that has a method getCardsForFight(cardId: number, titleFight: number).

[1]: https://github.com/cashapp/sqldelight