A modern programming language that makes developers happier.

kotlinlang

I've been testing Spine since yesterday and it's really great, thank you very much!

If you have any feedback, it's the perfect time! I'm planning on releasing 1.0 soon (a month or two hopefully)

It's not much, but I was a bit lost trying to find the documentation. First, I was on the OpenSavy site <https://opensavvy.dev/libraries/groundwork/spine.html|opensavvy.dev/libraries/groundwork/spine.html>, then I had to go to the repo to finally find <https://spine.opensavvy.dev/|spine.opensavvy.dev>

and then I wonder, why not want to use compiler plugin ?

Otherwise, I would have liked a very simple example repo that I could run myself; in principle, I find that more illustrative than documentation, but I'm struggling :slightly_smiling_face:

For now, I don't have enough perspective yet to give truly constructive feedback on the library itself, but I find it very cool to use.

Oh right, the OpenSavvy website should link to the Spine site directly

&gt; why not want to use compiler plugin ?
Because then I'd have to release a new version for every Kotlin version, and that'd be a massive pain especially if other people build libraries on top of it. Also, what would it even do? I can do everything I want within the rules of the Kotlin language itself

There's an entire example in a single file here: <https://gitlab.com/opensavvy/groundwork/spine/-/blob/main/server/src/commonTest/kotlin/RouteTest.kt?ref_type=heads>

&gt; Because then I'd have to release a new version for every Kotlin version, and that'd be a massive pain especially if other people build libraries on top of it. Also, what would it even do? I can do everything I want within the rules of the Kotlin language itself
Yes, I understand, it was just that Ktor resources have less boilerplate, but it's true that it's not worth it.

Spine does a _lot_ more than Ktor resources, though

<https://spine.opensavvy.dev/comparison-ktor-resources.html|spine.opensavvy.dev/comparison-ktor-resources.html>

yes that is why I want to use it :slightly_smiling_face:

Spine delegates serialization to Ktor ContentNegotiation, so any format should work.
Why does `HttpClient.request()` then set `Content-Type: application/json` by default?
Is that intentional, or should the Content-Type be left to the client / the installed converter?

With normal Ktor you have to specify the content type on every call: <https://ktor.io/docs/client-serialization.html#send_data|https://ktor.io/docs/client-serialization.html#send_data>
I'm not aware of a way to configure it as a global default.

Since it's a pain to do it each time, and I'm pretty sure most users want JSON anyway, I decided to make that the default

If there is a way to configure a global default, I'll change the Spine default to ‘whatever is the global default’

You can explicitly override `...request(..., contentType = ...)`yourself if needed

Server-side there is no default, content-negotiation is autonomous