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

CLI: switch to dedicated logging crate #236

Open
DaAlbrecht opened this issue Jan 19, 2025 · 1 comment
Open

CLI: switch to dedicated logging crate #236

DaAlbrecht opened this issue Jan 19, 2025 · 1 comment
Labels
A-CLI Related to the main CLI and not a more specific subcommand D-Straightforward Simple bug fixes and API improvements, docs, test and examples S-Ready-for-Implementation This issue is ready for an implementation PR. Go for it! X-Uncontroversial This work is generally agreed upon

Comments

@DaAlbrecht
Copy link
Contributor

A dedicated logging crate would be helpful to support options like --quite or --verbose. Additionally it would help to make the output messages more consistent.
@TimJentzsch TimJentzsch added A-CLI Related to the main CLI and not a more specific subcommand X-Uncontroversial This work is generally agreed upon D-Straightforward Simple bug fixes and API improvements, docs, test and examples S-Ready-for-Implementation This issue is ready for an implementation PR. Go for it! labels Jan 20, 2025
@TimJentzsch
Copy link
Collaborator

Logging crates currently used in Bevy:

  • tracing, which also can do a lot more than just logging.
  • log, which appears to be more light-weight. Used in Bevy for no_std support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-CLI Related to the main CLI and not a more specific subcommand D-Straightforward Simple bug fixes and API improvements, docs, test and examples S-Ready-for-Implementation This issue is ready for an implementation PR. Go for it! X-Uncontroversial This work is generally agreed upon
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TimJentzsch @DaAlbrecht