feat(qc-logging): add qc logging and basic type utils - #3
Merged
Conversation
Member
|
Changelog is auto-filled from commit messages |
metalwarrior665
approved these changes
Jul 24, 2026
metalwarrior665
left a comment
metalwarrior665
left a comment
Member
There was a problem hiding this comment.
isFalsy is definitely interesting, wonder how will thsi be used in the wild
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
3 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.
structured logging to measure usage or certain failure conditions using mezmo afterwards.
Should i modify the changelog in this exact branch or what?
All the overloading on functions is so rules like the oxlint/eslint ones mentioned still work when doing. (it was the simplest way for that to work)