ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

Public bug reported:

There is a recommended naming convention for QFlags types in the Qt
documentation: http://doc.qt.io/qt-5/qflags.html. Ok, we don't need to
use this exactly, but we should be consistent across our API. As I'd
like us to provide headers so we have a C++ API, we should fix this up
now in a way that doesn't break the QML API.

** Affects: oxide
     Importance: Low
         Status: Triaged

** Changed in: oxide
   Importance: Undecided => Low

** Changed in: oxide
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1533223

Title:
  Use consistent naming for QFlags

Status in Oxide:
  Triaged

Bug description:
  There is a recommended naming convention for QFlags types in the Qt
  documentation: http://doc.qt.io/qt-5/qflags.html. Ok, we don't need to
  use this exactly, but we should be consistent across our API. As I'd
  like us to provide headers so we have a C++ API, we should fix this up
  now in a way that doesn't break the QML API.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1533223/+subscriptions