Closed banillie closed 3 years ago
Common problem! To be honest, on first look I doesn't look that bad, but I see why it's painful. You could look at adding another or more subcommands, maybe. You probably just need a handler function of some kind that dispatches based on a single param. Few ways to do it dude. Will get in touch this week Will - on study leave this week.
Cheers dude. Hope the study leave isn't too hard!
Managed to resolve this via packaging all arguments into a dictionary op_args
and then unpacking that dictionary as kwargs into each class / function via **op_args
. This enabled me to delete many many many lines of code.
@yulqen how are you? Hope you have a good break.
I'm running into some very long and tedious if/elif/else loops as a means with layering in all the different options available to the user via the command line for analysis_engine. This is because some of the analysis needs multiple different optional arguments. For example this is what a command for milestones analysis could look like
analysis milestones --stage "FBC" --quarters "Q3 20/21" --dates "1/1/2021" "1/1/2022" --type "Delivery" --chart "show" --title "FBC schedule 2021/22"
.The if/elif/else loop for this currently looks like this:
Grateful for your advice on how this code could be refactored. Cheers, Will.