A modern programming language that makes developers happier.

kotlinlang

I'm still getting used to the way the IR compiler mangles field names. Should the tabulator module work with Kotlin models? I feel like my column definitions are going to be referencing field names that don't exist on the generated object.

You need to add `@JsExport` to your model data class.

Thanks. I know I've seen that mentioned but it's never seemed to work for me

And tabulator module should handle the conversion between kotlin class and js object.

going to try it now :slightly_smiling_face:

Still loving KVision on a daily basis. Thanks <@UFT11FKSP>

Found something I hadn't experienced before:
```
@JsExport
class Child(val name: String)

@JsExport
class Parent(val name: String, val child: Child)

fun Container.parentTable(parents: List&lt;Parent&gt;) {
    tabulator(
        parents, options = TabulatorOptions(
            columns = listOf(
                ColumnDefinition("Parent Name", "name"),
                ColumnDefinition("Child Name", "child.name"),
            )
        )
    )
}```
fails with:
`Uncaught TypeError: Cannot set property name of #&lt;Child_0&gt; which has only a getter`
    `at e.n._setNestedData (tabulator.min.js?7558:2)`
    `at u.setValueActual (tabulator.min.js?7558:5)`
    `at u.build (tabulator.min.js?7558:4)`
    `at new u (tabulator.min.js?7558:4)`
    `at e.n.generateCell (tabulator.min.js?7558:3)`
    `at eval (tabulator.min.js?7558:2)`
    `at Array.forEach (&lt;anonymous&gt;)`
    `at t.generateCells (tabulator.min.js?7558:2)`
    `at l.generateCells (tabulator.min.js?7558:4)`
    `at l.initialize (tabulator.min.js?7558:4)`

If I set the "name" fields to vars instead of vals then it's happy

This seems to work in my older project using legacy backend, so I think they're now actively removing setters from immutable fields

which must mess up whatever values (cloned or raw) tabulator uses

thought that was interesting. Obviously I can just have my UI model fields be mutable and convert between immutable data model and mutable view model as necessary

<https://github.com/olifolkerd/tabulator/issues/3261> seems related

Yes. I forgot to mention this. You need to have "vars" in your model.

See the showcase example:
<https://github.com/rjaros/kvision-examples/blob/master/showcase/src/main/kotlin/com/example/TabulatorTab.kt#L34>

Tabulator integration with IR backend is a pain! :slightly_smiling_face:

Yeah I'm looking forward to the benefits IR brings :joy: