The current implementation for dynamic blame history generates an html output file without any blame tables and uses the Flask server to load the blame tables for the requested root SHA on demand.
The html output file can overwrite existing html output files and is useless when the gitinspectorgui app has been closed. Therefore, creating any html output files for the dynamic blame history option should be avoided and instead, the generated html code should be sent directly to the Flask server via python.
davbeek
commented
2 weeks ago
The current implementation for dynamic blame history generates an html output file without any blame tables and uses the Flask server to load the blame tables for the requested root SHA on demand.
The html output file can overwrite existing html output files and is useless when the gitinspectorgui app has been closed. Therefore, creating any html output files for the dynamic blame history option should be avoided and instead, the generated html code should be sent directly to the Flask server via python.