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.

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

Add support for (internal) debug logging output #274

Merged
merged 1 commit into from
Oct 24, 2024

Conversation

atc0005
Copy link
Owner

@atc0005 atc0005 commented Oct 24, 2024

Overview

The changes provided by this commit were initially intended to provide a minimal abstraction to support toggling the size of plugin output off/on as needed for troubleshooting. From there the scope widened as further iteration showed that it could be useful to add debug logging support (internally for now) to the library as a whole.

To support toggling on/off specific debug log activity, debug log output is currently split into two categories:

  • debug logging of actions
  • debug logging of plugin output size

The intent of these changes is to provide a way to easily toggle on/off the internal workings of this library. If client code does not enable debug logging, the result should be this library working just as it did before.

The current implementation is subject to change as real world testing is applied and feedback collected.

Changes

  • allow toggling debug logging output on/off
  • allow toggling specific debug logging output on/off
    • e.g., allow all debug messages except for general plugin activity
    • e.g., allow only debug messages for plugin output size calculations
  • support setting custom debug logging output target
    • e.g., redirect debug log messages to a target file instead of stderr (the default debug log target)
  • add test coverage for new behavior

References

@atc0005 atc0005 added enhancement New feature or request tests output/logging plugin debug logging output intended for troubleshooting purposes labels Oct 24, 2024
@atc0005 atc0005 added this to the v0.17.0-alpha.3 milestone Oct 24, 2024
@atc0005 atc0005 self-assigned this Oct 24, 2024
OVERVIEW

The changes provided by this commit were initially intended to provide
a minimal abstraction to support toggling the size of plugin output
off/on as needed for troubleshooting. From there the scope widened as
further iteration showed that it could be useful to add debug logging
support (internally for now) to the library as a whole.

To support toggling on/off specific debug log activity, debug log
output is currently split into two categories:

- debug logging of actions
- debug logging of plugin output size

The intent of these changes is to provide a way to easily toggle
on/off the internal workings of this library. If client code does not
enable debug logging, the result should be this library working just
as it did before.

The current implementation is subject to change as real world testing
is applied and feedback collected.

CHANGES

- allow toggling debug logging output on/off
- allow toggling specific debug logging output on/off
  - e.g., allow all debug messages except for general plugin activity
  - e.g., allow only debug messages for plugin output size calculations
- support setting custom debug logging output target
  - e.g., redirect debug log messages to a target file instead of
    stderr (the default debug log target)
- add test coverage for new behavior

REFERENCES

- refs GH-264
- refs GH-271
@atc0005 atc0005 force-pushed the i271-add-support-for-debug-logging-output branch from ae2e3e3 to e38b98e Compare October 24, 2024 12:36
@atc0005 atc0005 merged commit f987eeb into development Oct 24, 2024
28 of 29 checks passed
@atc0005 atc0005 deleted the i271-add-support-for-debug-logging-output branch October 24, 2024 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request output/logging plugin debug logging output intended for troubleshooting purposes tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant