jackson-module-kotlin VS kotlin-wrappers

strictNullCheck option in the Kotlin module doesn't cover non-object-field situations at all. https://github.com/FasterXML/jackson-module-kotlin/issues/479

But, it sucked. I was constantly finding bugs related to nullability, around generics, inline/value classes, etc. And it wasn't the typical trivial ones, either. Figuring out that you're calling a Java library and encountering a "platform type" is the least problematic. My biggest struggle came from using libraries that were written in Java first, but then added a Kotlin API on top. So, my code didn't know I was dealing with a platform type and neither did I. Yet they were still broken. Some of them are broken in an unfixable way, such as JacksonXML's Kotlin module: https://github.com/FasterXML/jackson-module-kotlin/issues/479. So many Java libraries rely on reflection even when it's not obvious that they might, so you pretty much can't ever use value classes in Kotlin, including the unsigned number types.

You should add Jackson Module Kotlin in your project. After that, you can't specify a type of object explicitly.

Not really, you just need to handle some standard types and have a good extension mechanism to let the user implement factories. That library having built in support for UUID and datetime is probably a bit much, I'd prefer a plugin like https://github.com/FasterXML/jackson-module-kotlin

There is a bug at this very moment that makes it literally impossible to deserialize [1, 2, 3, null] into a List with Jackson's Kotlin module. Yes- even if you set KotlinModule(strictNullChecks = true). It's just broken. (Here's the link: https://github.com/FasterXML/jackson-module-kotlin/issues/479)

Got you, thanks. I didn’t mean to sound offensive - a better wording would be that they don’t seem to prioritize this part, at least based on https://github.com/FasterXML/jackson-module-kotlin/issues/199, which has one abandoned branch from a 3rd party and a couple of comments from from maintainers.

If you use Jackson, don't forget to include the Kotlin extensions https://github.com/FasterXML/jackson-module-kotlin

Did you include jackson-module-kotlin?

If you want something more standard, I'd look at Kotlin Wrappers and look at examples of using react - https://github.com/JetBrains/kotlin-wrappers

Kotlin wrappers for JS.

The only reference I can find to an error boundary in Kotlin React is at QueryErrorResetBoundary.kt in the kotlin-wrappers repository. Would any of you know anything about this?

Yes! Interesting that it isn't defined in the Length.kt file (that's where I was looking for it) and is instead in its lonesome, but I guess it makes sense as it's not actually a length value. Thanks for the help!

plugins { kotlin("js") id("com.github.node-gradle.node") version "3.4.0" } kotlin { js(IR) { // let's rename it to more reusable as under that name we will access it in our boilerplate code moduleName = "stories" // browser also works fine here, we just need it for compiling purposes as of now nodejs {} // add a startup script to our package json compilations["main"].packageJson { customField( "scripts", mapOf("storybook" to "start-storybook -p 6006 -c $projectDir/.storybook --ci") ) } binaries.executable() } } tasks.named("build") { dependsOn("assemble") dependsOn("copyJsStories") } tasks.register("copyJsStories") { dependsOn("developmentExecutableCompileSync") from("$projectDir/src/main/js") into("$buildDir/compileSync/main/developmentExecutable/kotlin") // flatten all files to appear on one level eachFile { if (isDirectory) { exclude() } path = path.replace("/", ".") } } tasks.register("copyPackageJson") { dependsOn("build") from("$buildDir/tmp/publicPackageJson/package.json") into("$projectDir") } tasks.register("start") { dependsOn("build") dependsOn("npmInstall") args.addAll("run", "storybook") } tasks.named("npmInstall") { dependsOn("copyPackageJson") workingDir.set(file("$projectDir")) inputs.file("package.json") } dependencies { // dependency to the project with components implementation(project(":app")) // react dependencies to put on package.json explicitly // can resolve the actual versions on https://github.com/JetBrains/kotlin-wrappers implementation(npm("react", "^17.0.2")) implementation(npm("react-dom", "^17.0.2")) implementation(npm("react-router-dom", "^6.2.2")) // storybook specific dependencies implementation(npm("@storybook/builder-webpack5", "^6.5.9")) implementation(npm("@storybook/manager-webpack5", "^6.5.9")) implementation(npm("@storybook/node-logger", "^6.5.9")) implementation(npm("@storybook/preset-create-react-app", "^4.1.2")) implementation(npm("@storybook/react", "^6.5.9")) }

kotlin js https://github.com/JetBrains/kotlin-wrappers/tree/master/kotlin-react Multiplatform etc.

From my experience if you're truly trying to interop with JavaScript code that is already out there on npm, you better hope there is a library that already wraps it like kotlin wrappers. Otherwise you would have to write a wrapper library yourself or use dukat to convert typescript definitions to kotlin (which I have never had the best luck converting but maybe it got better?).

Everything moved to central a long back - https://github.com/JetBrains/kotlin-wrappers

It's still pretty finnicky to configure and it hasn't emerged from alpha yet, so its future isn't exactly secure, but I'm hopeful as they appear to be investing a lot of resources into it and adjacent projects, e.g. the kotlin-react library.

We already have a battle-tested integration with react (it's used inside jetbrains.space) -- https://github.com/JetBrains/kotlin-wrappers And, take a look at docs and hands-on.