At the moment, all logging in sheet2linkml is carried out by running e.g.:
logging.info(f"Google Sheet loaded: {model}")
The recommended way of using loggers is to create a context specific or per-class logger object and use that, i.e.
logger = logging.getLogger(__name__)
click_log.basic_config(logger)
# code for module
logger.info(f"Google Sheet loaded: {model}")
(Note the use of click-log to allow users to configure the logging from the command line, so we no longer have to include a logger.ini file)
I'm going to mark this low-priority, since the current scheme works for now. However, new code should definitely use this scheme, and we should probably find some time towards the end of this year or early next year to do this.
At the moment, all logging in sheet2linkml is carried out by running e.g.:
The recommended way of using loggers is to create a context specific or per-class logger object and use that, i.e.
(Note the use of click-log to allow users to configure the logging from the command line, so we no longer have to include a logger.ini file)
I'm going to mark this low-priority, since the current scheme works for now. However, new code should definitely use this scheme, and we should probably find some time towards the end of this year or early next year to do this.