fix: document null as an accepted metric attribute value - #2185
Merged
Litarnus merged 1 commit intoAug 26, 2026
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Litarnus
approved these changes
Aug 26, 2026
Litarnus
left a comment
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Thanks for the contribution!
Sorry, something went wrong.
2 tasks
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
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.
Description
Attribute::tryFromValue() already accepts null and converts it to the string "null", but the public metric attribute type declarations (array<string, int|float|string|bool>) excluded null. This meant static analysis rejected null attribute values even though they work correctly at runtime, forcing callers (and wrapper implementations) to suppress type errors.
Issues
resolves: #2182