Is your feature request related to a problem? Please describe.
Currently the CadToCsg.start() method does quite a lot of stuff.
I'm thinking this could be broken down into stages to give more fine grain control to the user and make the code more testable.
Keen to see what others think
Describe the solution you'd like
A more modular approach that allows users to perform individual steps.
This is also be useful if we ever want to replace parts of the code based.
Here is an idea of what the steps could be
this has the advantage of moving some of the huge amount of arguments to where they are needed. We have already seen this with the export_csg which was able to delay the requirement of the user to specify the out_format to the final step and therefore save time if they want to change arguments relating to a single stage. For example the step_file could be passed to load_cad as no other function needs it.
This would also make it easer to test discreate functionality
Is your feature request related to a problem? Please describe.
Currently the
CadToCsg.start()
method does quite a lot of stuff. I'm thinking this could be broken down into stages to give more fine grain control to the user and make the code more testable.Keen to see what others think
Describe the solution you'd like
A more modular approach that allows users to perform individual steps. This is also be useful if we ever want to replace parts of the code based. Here is an idea of what the steps could be
this has the advantage of moving some of the huge amount of arguments to where they are needed. We have already seen this with the
export_csg
which was able to delay the requirement of the user to specify theout_format
to the final step and therefore save time if they want to change arguments relating to a single stage. For example thestep_file
could be passed to load_cad as no other function needs it. This would also make it easer to test discreate functionalityDescribe alternatives you've considered
keeping the code structure as it currently is