generated from PlexSheep/baserepo
logger documentation outdated and low detail #74
Collaborator
- the build methods still use the old names in the documentation
- the logger struct / module does not explain in detail how the logger works
- Make it very explicit that users should use the macros and that the struct is only for use in contexts where that is not possible
- explain the log levels neatly
- add a fancy ascii diagram to explain when to use the log levels?
- document the pub use statements
- explain how logging to file works in detail
- write to file example
- [x] the build methods still use the old names in the documentation
- [x] the logger struct / module does not explain in detail how the logger works
- [x] Make it very explicit that users should use the macros and that the struct is only for use in contexts where that is not possible
- [x] explain the log levels neatly
- [x] add a fancy ascii diagram to explain when to use the log levels?
- [x] document the pub use statements
- [x] explain how logging to file works in detail
- [x] write to file example
Kind/Documentation
Reviewed
Confirmed
Priority
High
labels
Add default values to LoggerBuilder #82
Priority
Medium
and removed Priority
High
labels
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference: PlexSheep/pt#74
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?