The logging approved has been implemented. Here the finales_log.log file will log interaction in the server backend.
To accommodate this raising of value and runtime errors should be handled through the logging class as shown. All places where errors are raised has been changed
Original draft for suggestion:
I have been contemplating on how to perform the logging in the most convenient way.
This draft is quite convenient for logging everything in the backend. A class with configuration of the log is created. This is then imported in the init files in folders that have actions in the backend, such as the cli and server folders
One drawback is the log from the uvicorn package is not logged, meaning all server action responses in the terminal output is not gonna be present. This however seems like quite complicated, and the people who manage to do so lose some formatting functionality such as colors in the output
Let me know what you think
Testing why the checks fails for the logging PR
The logging approved has been implemented. Here the finales_log.log file will log interaction in the server backend. To accommodate this raising of value and runtime errors should be handled through the logging class as shown. All places where errors are raised has been changed
Original draft for suggestion: