-
Type:
Spec Change
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Component/s: Logging
-
None
-
Needed
Summary
The truncation section placed "MUST handle gracefully" (Unicode code points) and "MUST implement naively" (JSON structure) in the same sentence, making them appear contradictory. Rewrite to make clear they apply to different concerns.
Motivation
Who is the affected end user?
Driver authors implementing logging truncation.
Is this issue urgent?
No.
Is this ticket only for tests?
No — spec text clarification.
Acceptance Criteria
PR merged: https://github.com/mongodb/specifications/pull/1937
- related to
-
DRIVERS-3519 Spec analysis: logging — missing tests, ambiguities, inconsistencies
-
- Backlog
-
- split to
-
CDRIVER-6332 Clarify logging truncation: Unicode code point safety and naive JSON are separate concerns
-
- Blocked
-
-
CSHARP-6045 Clarify logging truncation: Unicode code point safety and naive JSON are separate concerns
-
- Blocked
-
-
CXX-3494 Clarify logging truncation: Unicode code point safety and naive JSON are separate concerns
-
- Blocked
-
-
GODRIVER-3910 Clarify logging truncation: Unicode code point safety and naive JSON are separate concerns
-
- Blocked
-
-
JAVA-6204 Clarify logging truncation: Unicode code point safety and naive JSON are separate concerns
-
- Blocked
-
-
NODE-7584 Clarify logging truncation: Unicode code point safety and naive JSON are separate concerns
-
- Blocked
-
-
PHPLIB-1852 Clarify logging truncation: Unicode code point safety and naive JSON are separate concerns
-
- Blocked
-
-
PYTHON-5827 Clarify logging truncation: Unicode code point safety and naive JSON are separate concerns
-
- Blocked
-
-
RUBY-3879 Clarify logging truncation: Unicode code point safety and naive JSON are separate concerns
-
- Blocked
-
-
RUST-2427 Clarify logging truncation: Unicode code point safety and naive JSON are separate concerns
-
- Blocked
-