Can I use kotlin serialization in kotlin script?

Thank you!

Most of the times, I use

kotlinx-serialization-json

without the compiler plugin. It's not as type safe but for scripts, it's often "good enough"

I need xml

You can do stuff like

"{}".parseToJsonElement()

Let me try

Then you can cast/get children as needed

not much of a reason to use kxs over java.xml if you're not going to use the generated serializers though

true

Yeah, that is my next option is just take java library

one reason is that it's only one maven coordinates to remember 😄

java.xml module is part of the JDK, no maven coordinates at all 😛

Ahaha even better !

oh it was there pre-modularization, just not as a module

👍

I don't think there's any object mapping built in. I guess Jackson would work if you need, since that's all reflection-based and not compile-time

FWIW, I just remembered I wrote this: https://github.com/martinbonnin/xoxo It's very simple, not tested a lot (I think I'm the only user 😄 ) but feedbacks are welcome!

You could even use serialization with serializers fine in a Kotlin script. You just cannot define new serializable objects that have default serilalizers provided by the compiler plugin as you cannot right now apply the compiler plugin. But you could have serializable objects with custom serializers and you can use classes that were compiled with the compiler plugin.

Oke people, thank you. I’m just trying to cook a quick scrip to automate translations of some different yaml files with DeepL

Put it back at to the end of the pet projects circular queue 😄

@Vampire

You just cannot define new serializable objects that have default serilalizers provided by the compiler plugin as you cannot right now apply the compiler plugin.

I'm not sure I understand, what is missing. There are two tests in the Kotlin repo that run this script - https://github.com/JetBrains/kotlin/blob/1.8.20/libraries/tools/kotlin-main-kts-test/testData/hello-kotlinx-serialization.main.kts - which uses plugin to generate serializers. You can add the plugin either via CLI, if cli compiler is used, or via compiler configuration.

Yeah, you are right @ilya.chernikov. If you call

kotlinc

explicitly, or call the script from a bash script or similar, or call the script programmatically. But there is no way to make it work with calling

./hello-kotlinx-serialization.main.kts

. See the Ticket @ephemient linked above. Note: the shebang hack is not appropriate for general usage. You either require a non-standard environment variable or an absolute path, and more important using more than one argument in the shebang line must be avoided for general usage, it is undefined and not portable and will behave majority different on different systems.

you could probably pull off some sort of polyglot trick. for example,

#!/bin/sh
//bin/true<<.
/*
.
# any shell script goes here
kotlin "$0" "$@"
exit $?
*/
// any Kotlin script goes here
println("Hello, world!")

where you can put an arbitrarily complex shell script in there that Kotlin will skip over

Oh, amazing. Ugly, but amazing. 😄

grrrr windows paths

Yay, thought about how to do it with colon, but didn't think about that quote trick, "nice" 😄

oh I see, if you need annotations that is tricky

So it seems the "best" way might indeed be

#!/bin/sh

///bin/true <<EOC
/*
EOC
kotlinc ...
exit $?
*/

...

"just" implement a maven resolver in shell and download the kotlin compiler and plugin 🤪

Yep, exactly. 😄

Did you try just throwing it at chatGPT and say sth like: translate this to XYZ?

Nice, it is second suggestion try to use ai for thisbtask

Well, chatGPT is a fancy toy and nothing more imho. Imo you can only ask it to do work you could also do yourself and know exactly what the result should look like to fix the non-sense it produces, but just are too lazy to write yourself from ground up. All tries to let chatGPT generate code so far that I've seen was producing more ore less non-sense. It produced totally wrong code or missed important parts it only added after you told it to, or used methods on APIs that do not exist and never did exist at all. Besides that its data base is older than 2 years which is really very long in software development terms.

it's prone to making stuff up, but so is DeepL

How is a translator prone to making things up?

I've seen it add context to translations that completely doesn't exist in the source

Ok, I guess I keep sticking with Google translate. :-D

Google Translate has failures too. the big thing with DeepL and ChatGPT is that their output tends to sound more fluent even when it's totally wrong

Yeah, which is a big problem. Even worse than people copying SO answers blindly.

It's fine, you just need a human going over it in the end

That's what I said. You can only use it for things you could have done yourself, so that you can see where the non-sense is and fix it. So if you let the tool translate something from Arabic to Russian, you need someone speaking both languages to fix up the result, that could have done the work himself right away.

Bjorn, I can clean room floor with vacuum cleaner just by myself or I can finish the corners after vaccum cleaner robot. That are both possible ways to finish that task.

Yes, that's exactly what I said. If you could have done it yourself but are too lazy or whatever, you can let the tool do it and fix its non-sense. But if you don't have arms or are blind (not speaking Arabic or Russian), then you cannot fix the non-sense and should not depend on the result.