Absolute extrusion about roboxslicerextension HOT 3 CLOSED

I think we should follow DRY principles as much as possible, which means making everything as generic as possible, and only overriding things that are actually different for each slicer.

I believe that abstract classes can have methods (and code inside those methods), so I'd prefer to put as much code as possible inside the parent "Slicer" class. It might take some clever thought to work out where the line should be drawn between the parent class and the children.

from roboxslicerextension.

Go for it. And let us not being afraid refactoring if we think of a better way! :)

from roboxslicerextension.

ok good news I love DRY code, I will move my code to the parent.

from roboxslicerextension.