Drop decode_document_utf8_lossy

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • bson-0.15.0
    • Affects Version/s: None
    • Component/s: BSON
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The bson library provides two Document decoding functions, one that allows lossy uft8 string decoding and one that does not. The difference being if a buffer containing BSON bytes has invalid utf8 strings in either the keys or values, decoding will still succeed and just put a replacement character where the invalid bytes were.

      It is unclear why we provide this functionality / how it is useful to users. We should drop it prior to 1.0.

              Assignee:
              Isabel Atkinson
              Reporter:
              Patrick Freed
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: