would an interface with those 3 fields work for yo...

# getting-started

[menegatti]

would an interface with those 3 fields work for you?

[nayanjyoti]

menegatti: I was hoping of doing it in another way.

[nayanjyoti]

interfarce would be too clumsy as override is needed in both

[marstran]

You could use delegation to do something like this:

interface A {
    val fieldA: String
    val fieldB: String
    val fieldC: String
}

data class FirstClass(
        override val fieldA: String, 
        override val fieldB: String, 
        override val fieldC: String) : A

data class SecondClass(val firstClass: FirstClass, val fieldD: String) : A by firstClass

[nayanjyoti]

The extra interface declaration is bugging me. if there was any other way..

[menegatti]

there isn't any

[menegatti]

really, if you're just trying to prevent typing the parameters use multi-cursor or have template to use

[menegatti]

if the objects share no behavior and you don't want to have a base class, then there's nothing the language can help you with

[marstran]

If the classes are conceptually related, I think it really does make sense to extract that interface.

[marstran]

But if they just coincidentally have the same fields, don't do it.

[nayanjyoti]

They are request-response for a particular web service, and i find it not suitable to extend an interface. Currently, I ended up copying the same fields to the other classes as well. the other class does have few extra fields as well.

[menegatti]

then maybe they are related

[menegatti]

if all (or most of) your requests have the same fields

[menegatti]

then they share behavior and the interface becomes the right modelling there

[nayanjyoti]

I meant these two were the request and response for one webservice. the other requests and response don’t share the similar behaviour.

[menegatti]

I see