Confluence Rest API v2 IDs are in int64 which cannot be safely represented in JavaScript

XMLWordPrintable

    • Major

      Issue Summary

      Some Confluence sites use ids greater than 253 - 1 (the safe upper limit that JavaScript can represent). This poses a problem with the v2 REST API as ids are represented as int64's. Instead, they should be offered as strings so they can be safely parsed. 

      String-typed, temporary ID fields will be added alongside the existing numeric ID fields in the short-term. Long-term, the existing ID fields will be transitioned to a String and the temporary fields removed. 

      Steps to Reproduce

      1. Make calls to Confluence REST v2 API
      2. Observe numeric id fields in JSON response (instead of Strings)

      Expected Results

      N/A

      Actual Results

      N/A

      Workaround

      No viable workaround currently exists. A String field will be added to the response of these endpoints  

            Assignee:
            Simon Kliewer
            Reporter:
            Alex Williams
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: