I there a reason why methods in `interface Container` returns Container? I can't see any usecase wh...

# kvision

[Tomas Kormanak]

I there a reason why methods in interface Container returns Container? I can't see any usecase where it could be useful and I don't think it's a good pattern (fluent interface). I think they should return Unit The only case I can imagine return something else is method add. It can return added component to support this shortcut:

val mycomponent = add(MyComponent())

[Tomas Kormanak]

Right now this is possible

SimplePanel().add(x).add(y).add(z)

But I think KVision should not allow it in favor of this:

SimplePanel().apply {
    add(x)
    add(y)
    add(z)
}

[Robert Jaros]

I hardly ever use any of container methods directly myself ;-)

[Tomas Kormanak]

In the first case you can't be sure you are still working with the same instance.

[Robert Jaros]

You are probably right. Please fill an issue for KVision 6 🙂

[Tomas Kormanak]

btw: good post about this:
https://ocramius.github.io/blog/fluent-interfaces-are-evil/

[Tomas Kormanak]

Are you already working on version 6? I have bunch of ideas:)

[Robert Jaros]

No, I don't 🙂 But breaking changes are allowed in major releases only 😉

[Robert Jaros]

@Tomas Kormanak Now it's the right time for KVision 6 ideas 😉