Code maintainability - utils/__init__.py split (?) #1677
Labels
design-discussion
good first issue
hackathon
Good issues for the upcoming bluesky hackathon
maintenance
At the moment the class in question is 1870 lines of code. Some of them do with await logic, some are syntactic sugar, some format outputs (ProgressBar), callbacks (CallbackRegistry), and control signals (SigIntHandler).
Expected Behavior
We get about a dozen files in
/utils
instead.Current Behavior
Easier to locate where a change needs to happen and to recognize what changed.
Possible Solution
Just a new file for every logical chunk - likely bundling 2-3 connected classes at a time, or a set of functions all dealing with one functionality.
The text was updated successfully, but these errors were encountered: