Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: summary events should allow null default value in counter (#253)
When testing dotnet client, I came across the behavior that a `null` default value will end up in a summary event counter as the key `"default": null`. This isn't accepted by the test harness, even though our JSON standard mandates that null and an omitted property be treated equivalently. The SDK could fix this by omitting the property - but the harness should also accept this. ----- I'm open to hearing "no, the harness should not accept this."
- Loading branch information