fix: output monitor input names instead of codes if we have them - #408
Merged
Merged
Conversation
newAM
approved these changes
Oct 21, 2025
newAM
left a comment
newAM
left a comment
Owner
There was a problem hiding this comment.
Thanks! Sorry for the slow review, I'm on the road a lot for work, it may take a couple weeks before I get to the others you opened.
Contributor
Author
No apologies necessary! I'm used to these kinds of projects being completely abandoned so I'm just happy that I can contribute to this one! |
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.
Simple PR; if we have a name for the MonitorInput, print it; otherwise, print "UNKNOWN" with the monitor code.
Also added some minor cleanups:
sys.stdout.writewithprint(since I couldn't see any indication of whether there was a necessity to usesys.stdout.writespecifically)