D8139: Add missing X-KDevelop-Category entries to plugins' metadata

Friedrich W. H. Kossebau noreply at phabricator.kde.org
Fri Oct 6 14:35:29 UTC 2017

kossebau added a comment.

  In https://phabricator.kde.org/D8139#152657, @mwolff wrote:
  > Great work, I wonder if we could get some basic plugin json validator integrated into our buildsystem... would be useful for such situations, I guess!
  Yes, having a data validation build step would be good in general, agreed very much. In old times people used the validation checks in krazy for this, but these days krazy/EBN seems to be out of people's view, and then krazy also misses out any data generated/modified at build time.
  IMHO ECM would/could provide a generic approach to this, so common data schemes could be covered out of the box and checks for custom ones could be added easily.
  Right now we only have appstream data validation hacked into KDECMakeSettings.cmake. Which is such a lazy hack that it makes me cry everytime I see it ;)
  CI could then take over some task from EBN.

  R32 KDevelop


To: kossebau, #kdevelop, brauch
Cc: mwolff, brauch, kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20171006/503ba567/attachment.html>

More information about the KDevelop-devel mailing list