Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-12740

Don't round coverage data in the webapp, but on the backend

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Web, Web API
    • Labels:
      None
    • Edition:
      Community
    • Production Notes:
      None

      Description

      In SONAR-12256, we reported an issue with rounding, where coverage data was rounded in one way in the measures panel, and another way in the failing QG box.

      At the time, we thought this was due to a rounding error in the frontend, but it turns out this rounding discrepancy happens on the backend. The frontend code to manage this is pretty complex, and adds a significant overload for something as simple as formatting a number. The rounding should be fixed and made consistent on the backend, regardless of context, and we should remove the fix on the frontend, and only display the data as-is.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              wouter.admiraal Wouter Admiraal
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated: