i see.. i wonder if i can work around that.. but i...

# announcements

[Nikky]

i see.. i wonder if i can work around that.. but it seems impossible.. so setter and getter copypasta..

[Andreas Sinz]

@Nikky So you basically have one giant class with a lot of properties, but only a subset of those should be available in a specific DSL part?

[Nikky]

yeah, basically.. mainly dues to historical reasons
the class selfreferences and that had to be serialized to Yaml/Json
sealed classes broke the Jackson parser for me .. so i just ended up dumping all in a single data class

[Nikky]

also the DSL seems towork well (although needing more code than i want)
next step is to make it possible to use from .kts files

[Andreas Sinz]

@Nikky you could try to use interfaces instead, e.g.

interface Foo {
    var foo: Int
}

interface Bar {
    var bar: String
}

data class FooBar(var foo: Int, var bar: String) : Foo, Bar 

dsl<Foo> {
    //only "foo" available
}

dsl<Bar> {
    //only "bar" available
}

[Nikky]

ohh i will try that soon, that way i can mix them as i want, i id not do this before because i think.. i still had to copy values to make the constructor work, but maybe i can get around that