All code should be automatically formatted, as an easy way to enforce the coding style.
The most likely tool we should use for that is clang-format.
All code should be automatically formatted, as an easy way to enforce the coding style.
The most likely tool we should use for that is clang-format.
One blocking issue is that Q_SLOT: is not recognized (but it will with clang 3.9), so either we use slots: or wait for clang 3.9
We now have a .clang-format config in both kube and sink. No enforced automatic formatting happening yet though.
This has gotten some more attention:
https://phabricator.kde.org/D24568
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/381
https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/199
https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/20
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/484
https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/47
Also okular has it already integrated, but with a custom clang-format config file and not the one provided from ECM.
It is still debatable if we can utilize it for the big plasma projects, because it will cause a lot of issues with the currently open MRs. Maybe we should format the components individually, for example runners, kcms etc.