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
Added proper errors handling for config and fixed multiple logger instances being created #226
base: main
Are you sure you want to change the base?
Conversation
fetch the latest changes and resolve the conflicts. |
@ARajgor The conflicts has been resolved |
Co-authored-by: Israel Antonio Rosales Laguan <israellaguan@gmail.com>
Co-authored-by: Israel Antonio Rosales Laguan <israellaguan@gmail.com>
@Israel-Laguan If the review is done, can this be merged? I can understand you must be very busy but conflicts are piling on as new commits are being pushed to the main branch. :) |
Yeah I think it can be merged, no problem from my side |
@Israel-Laguan Can you merge it as I don't have write access |
return cls._instance | ||
|
||
cls._instance = super().__new__(cls) | ||
cls._logger = LogInit(pathName="logs/core.log", console=True, colors=True) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
log path is fetch from config file. we are saving it in data/logs/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can't fetch from config file here as it needs to handle the case when the config file is missing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sample.config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better of we can avoid IO here as there won't be any way to handle any errors as not even the logging will be enabled. Like what if the user incorrectly edits the sample.config and there is some mistake.
If you are sure that this won't be a concern I can update the code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or if the user renamed config.example to config etc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also why creating new logger? just fetch from logger file and log it. so it will be in one file and simple
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logger will not be initialised at this point, importing here will cause cycling import
@Israel-Laguan any updates ? |
Bro I don't have write access either |
@ARajgor would be able to help |
Changes
route_logger
to directly access logger instead of requiring an additional parameterMissing Key
Before
After
Missing
config.toml
Before
After