-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: refactoring of the codebase is needed #99
Comments
Can you describe what you believe needs to be done ? |
The inclusion of multiple transcribers with many options like diarization, summary creation, and topic detection has made the code a lot bloated. There are a lot of if else ladders that can be simplified. Also, the methods do not follow the SOLID principles. I'd like to address those issues and thus make the code a bit more maintanable. |
Refactor StrategyHere, I outline a general idea for refactoring the codebase using an object-oriented approach. Application WorkflowPre-process source files
Current approach for detecting and specifying the source type and the corresponding processing is manual using
Transcription
The corresponding codebase can be easily ported. Post-process generated files
Again, all the corresponding functionalities can be easily ported.
|
Codebase has been refactored using an object-oriented approach into a structured four-stage process. Most of the work has been done with #118 and 2764a7f, with additional changes in miscellaneous commits that can be found in the git history. |
No description provided.
The text was updated successfully, but these errors were encountered: