Use a private property for the cached hexString ObjectId representation

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: BSON
    • Not Needed
    • 🔵 Done
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      As a Node driver engineer,
      I want to use native private fields instead of a weakmap to store cached hex strings,
      So that we can stay up-to-date with modern syntax.

      User Experience

      • Unaffected.

      Dependencies

      • n/a

      Risks/Unknowns

      • n/a

      Acceptance Criteria

      Implementation Requirements

      • Remove the weakmap in ObjectId.ts and instead use a private property to store the cached hex string on the ObjectId when caching is enabled.

      Testing Requirements

      • None.

      Documentation Requirements

      • none.

      Follow Up Requirements

      • none.

            Assignee:
            Unassigned
            Reporter:
            Bailey Pearson
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: