Feat/parallel plot

[Tanguylo]

[Tanguylo]

Not yet ready

[GhislainJ]

Are these getters and setters necessary ?

[Tanguylo]

Yes they are since default values are not the same in parent and children

[GhislainJ]

Why can't the children just overwrite the default value to its own ?

https://www.typescriptlang.org/play?#code/MYGwhgzhAECC0G8BQ1XWAewHYQC4CcBXYXDfAChTWoAdCAjEAS2GhvwxoC5o98msAc2gBeaACIw4qqgCUiaAF8kypKEgwAQohnpsfYqQq7aDZq3acefAcLHj606vIRKVSNftzQwo6FgBTAHc4clkAbk8cb3o-QJDNMMioiAwQAIA6EAxBcnF4HnEAGh8MyxoS8U1i6HoyjhpZJCA

[Tanguylo]

I am also questioning about that.

But what is clear is that you cannot expect this to work as expected:

class Parent {
    attribute: type = X;
    constructor() {
       this.function(attribute)
    }
}

class Children extends Parent {
    attribute: type = Y;
    constructor() {
       super()
    }
}

Here, the used value of attribute in children when running the constructor (which is what you want to do) will be X and not Y; because at this moment in the run of constructor, you are still in Parent class, although you are creating a Children instance.

To avoid this behavior, the Internet gives us the above trick.

[Tanguylo]

https://www.typescriptlang.org/play?#code/MYGwhgzhAECC0G8BQ1XQA4FcBGICWwGATgPboBc0EALkXgHYDm0AvNAERjsppa4HRGjSmHoBPANw9UwEvRpFMwaiSIAKAJSJpaVNQAWeCADoVKtQaPH0pdBp0BfHX3yEzJNTbJbku3ZZMhVmIyKV0nJyRQSBgAIWgAUwAPagT6ABMYeF9eHFcQiipaBmY2dmxuXVl5WiUVdR8dXQhMdASGxyRI6ppoMGD6BIB3OE0pHupobAHh6FixpCi5CBIQBOMQEkY1dnhKdgAaPuMhI-ZYw6mTxnsgA

[GhislainJ]

Ok, I think this case made me understand what is the difference between inside/outside attribute assignment in js, which was not clear at all to me before.

They are actually not equivalent, after all. I think on the other side, that they are a bit similar to python's class attribute vs attribute, even if they are not the same.

Considering this thread, class fields (outside the constructor), are called after the constructor which leads to the shown behavior.

Actually, the prop attribute in our test case, is not static nor a class field, its a plain "instance attribute". In this case, I think we should then use the constructor syntax, even if its a bit more cumbersome (still less cumbersome than getters/setters, which usage is unclear) :

https://www.typescriptlang.org/play?#code/MYGwhgzhAECC0G8BQ1XQA4FcBGICWw0A5kQFzRgB2AngNwprAD2lEALgE6bBtMcAUDNGiy4CGDk3Tl2HPJSLQAvNABEYVUOgBKRFuFsAFnggA6dJPTKJU+sIPGzvXv21aAvltH5Czpq717NCMTUxJrELMLWw8kTyRQSBgAIWgAUwAPNjTKABMYeGRhZlZObl4BfREcHxtpaFl5RRVVbE1hXSKghsx0NIFo9DdhT3iS9gprSjSAdzhXenG2aGwp2ehkhaQElggmEDTTECYiflV4clUAGgowohvVZOuVu7cgA