Expose a function to get the Thing logger - #394
Merged
Merged
Conversation
This should make it easier for Thing-adjacent code that's not part of a Thing to log in a way that shows up in invocation logs.
Barecheck - Code coverage reportTotal: 97.31%Your code coverage diff: 0.00% ▴ Uncovered files and lines
|
julianstirling
approved these changes
Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This should make it easier for Thing-adjacent code that's not part of a Thing to log in a way that shows up in invocation logs.
I've added a function
lt.get_thing_loggerthat will return the parent of all the Thing loggers - any child of this logger will show up in invocation logs.Closes #364