Deprecate BSON Timestamp methods that are not applicable to Timestamp

XMLWordPrintableJSON

    • 3
    • Not Needed
    • None
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • Not Needed
    • 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... user of the BSON library
      I want... a clear indication of which methods are relevant to the Timestamp class
      So that... I don't inadvertently use an API that will lead to unexpected results

      User Experience

      • Timestamp methods that are inherited from Long but do not apply to Timestamp are marked deprecated

      Dependencies

      Risks/Unknowns

      • Full list of methods TBD

      Acceptance Criteria

      Implementation Requirements

      • functional reqs, potential snafus to avoid, performance targets, etc

      Testing Requirements

      • N/A

      Documentation Requirements

      • DOCSP ticket, API docs, etc

      Follow Up Requirements

      • Sync on strategy for addressing NODE-2624 and update that ticket accordingly

            Assignee:
            Johnathan Martell
            Reporter:
            Daria Pardue
            Sergey Zelenov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: