Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Written logs should be structured by command and subcommand #95

Open
hampuslidin opened this issue Dec 18, 2022 · 1 comment
Open

Written logs should be structured by command and subcommand #95

hampuslidin opened this issue Dec 18, 2022 · 1 comment
Labels
A-logging Area - Logging C-enhancement Category - New feature or request C-good-first-issue Category - Good for newcomers D-medium Difficulty - Medium P-medium Priority - Medium

Comments

@hampuslidin
Copy link
Contributor

Currently, it is sorted as dates and times. Create another structure level that mirrors the CLI command/subcommand structure, for easier navigation of the relevant logs for a particular command.
@hampuslidin hampuslidin added C-enhancement Category - New feature or request C-good-first-issue Category - Good for newcomers D-medium Difficulty - Medium P-medium Priority - Medium A-logging Area - Logging labels Dec 18, 2022
@hampuslidin
Copy link
Contributor Author

Once #117 is merged, this could be implemented by adding a field on LoggerBuffer which says which command it should be for. module_path!() could be utilized at callsite for determining the current command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-logging Area - Logging C-enhancement Category - New feature or request C-good-first-issue Category - Good for newcomers D-medium Difficulty - Medium P-medium Priority - Medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hampuslidin