Logging API not implemented
Bug #1723461 reported by
Stefan Paetow
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Moonshot ID Selector |
New
|
Medium
|
Unassigned | ||
Bug Description
It appears that the Moonshot ID selector was supposed to have a form of logging implemented. It references Log4Vala, but since this is not being used, there is no logging implemented. Let's please implement an atomic (as in it opens the file, writes its message and closes the file) logging interface internally that responds to logging levels being set.
Thanks.
Revision history for this message
| Alejandro Perez (alejandro-perez-mendez) wrote | #1 |
To post a comment you must log in.
As part of my work for creating a CLI UI, I implemented a basic yet functional logger, that writes log messages to the file indicated in the MOONSHOT_LOG_FILE environment variable. If the variable is empty, it does nothing, as the current logger :).
You can find the code here:
https:/
Regards