Standardise compass coding style to use async/await

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • No version
    • Affects Version/s: None
    • Component/s: Tech debt
    • None
    • Not Needed

      Most of compass is still using node-style callbacks (with error as the first parameter).  There are a few promises scattered here and there as well and already some async/await here and there.

       

      Should we modernise it all to use async/await?

       

            Assignee:
            Unassigned
            Reporter:
            Le Roux Bodenstein
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: